Plan Scope Management

Plan Scope Management

-Rikesh Mathew

Plan Scope Management

Plan Scope Management

Project Integration Management is the specific responsibility of the project manager andit cannot be delegated or transferred. The project manager is the one that combines theresults from all the other Knowledge Areas to provide an overall view of the project. Theproject manager is ultimately responsible for the project as a whole.Projects and project management are integrative by nature, with most tasks involvingmore than one Knowledge Area.The relationships of processes within the Project Management Process Groups andbetween the Project Management ProcessProject Integration Management is about:Ensuring that the due dates of project deliverables, the project life cycle, and thebenefits realization plan are aligned;Providing a project management plan to achieve the project objectives;Ensuring the creation and the use of appropriate knowledge to and from theproject;Managing project performance and changes to the project activities;Making integrated decisions regarding key changes impacting the project;Measuring and monitoring progress and taking appropriate action;Collecting, analyzing and communicating project information to relevantstakeholders;Completing all the work of the project and formally closing each phase, contract,and the project as a whole; andManaging phase transitions when necessary

PM Process Group

: Planning

Knowledge Group
PM Knowledge Area

Scope

Scope Knowledge Area

What does it do?

  • Does 3 main things:
      1. Determine how scope is defined
      2. Document how scope is validated
      3. Plan how scope is controlled
  • Helps control scope creep – uncontrolled increases to your scope unless it goes through approved change request
  • It is a subsidiary plan of the Project Management plan

Key Benefits

  • Refines Project Charter
  • Provides guidance on how scope is managed
  • Provide direction on managing the project throughout its lifecycle

ITTO

Inputs

1. Project Charter
  • Contains high level project description and deliverable characteristics
  • Provides context to plan the scope management plan
2. Project Management Plan
  • Outlines how the end goal is achieved
  • Includes all approved subsidiary plans mainly
      1. Quality management plan: The way the project and product scope will be managed will be influenced by the organizations quality policy
      2. Project life cycle description: Series of phases that a project must pass through from beginning to end
      3. Development approach: Whether waterfall, adaptive, iterative, agile approach is used.
3. Enterprise Environmental Factors (EEF)
  • We have no control over these factors but they can impact our project
    1. Organizational Culture
    2. Infrastructure
    3. Personnel Administration
    4. Maketplace conditions
4. Operational Process Assets (OPA)
  • The way your organization wants you to run your projects which includes templates
  • Includes the 4 P’s – Plan, Processes, Procedures & Policy
  • Historical Information
  • Standardised guidelines and work instructions.

Tools & Techniques

1. Expert Judgement
  • Groups or Individuals with specialised knowledge to determine how we can manage scope
2. Data Gathering
  • Includes all the way to analyse data and choosing the best way.
3. Meetings
  • Project teams meet to develop scope management plan

Outputs

1. Scope Management Plan
  • Doesn’t tell you what your scope is but helps advice you on how you manage scope.
  • It is a subsidiary plan to Project management plan
  • Reduces risk of scope creep
  • It is an input to all other scope processes
  • The components include
      1. Process for preparing scope statement
      2. Process for creation of WBS from the scope statement
      3. Process for establishing how scope baseline will be approved and maintained
      4. Process that specifies how formal acceptance of the completed project deliverables will be obtained
2. Requirements Management Plan
  • Describes how your requirements will be analyzed, documented and managed
  • Components include
      1. How requirements activities will be planned, tracked and reported
      2. Configuration management activities 
          • How changes are initiated
          • How impacts are analysed
          • How impacts are tracked
          • Authorization levels to approve changes
      3. Prioritization of requirements
      4. Metrics used and why
      5. Traceability structure which reflects the requirements and checks if they are completed

Leave a Comment

Your email address will not be published. Required fields are marked *