Project Scope Management

Project Scope Management

1. Processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully. .

   • Managing the project scope is primarily concerned with defining and controlling what is and is not included in the project..

2. 1. Plan scope management

   • process of creating a scope management plan that documents how the project scope will be defined, validated, and controlled
   • Inputs
     • P.M plan
       • Approved subsidiary plans of the project management plan are used to create the scope management plan and influence the approach taken for planning scope and managing project scope.
     • Project charter
       • Used to provide the project context needed to plan the scope management processes.
     • Enterprise environmental factors
       • Marketplace conditions
       • Organizational culture
     • Organizational process assets
       • Organizational standards
       • Processes and procedures
   • Tools & techniques
     • Expert judgement
       • Refers to input received from knowledgeable and experienced parties.
     • Meetings
       • Attendees at these meetings may include the project manager, the project sponsor, selected project team members, selected stakeholders, anyone with responsibility for any of the scope management processes
   • Outputs
     • Scope Management Plan
     • Requirement management plan

3. 2. Collect requirements

   • Inputs
     • Scope manangement plan
       • Provides clarity as to how project teams will determine which type of requirements need to be collected for the project.
     • Requirements Management Plan
       • Provides the processes that will be used throughout the Collect Requirements process to define and document the stakeholder needs
     • Stakeholder Management Planl
       • Used to understand stakeholder communication requirements and the level of stakeholder engagement in order to assess and adapt to the level of stakeholder participation in requirements activities.
     • Project charter
     • Stakeholder register
       • identify stakeholders who can provide information on the requirements
   • Outputs
     • Requirement documenation
       • How individual requirements meet the business need for the project.
     • Requirement traceability matrix
   • Tools & techniques
     • Interviews
     • Focus Groups
     • Facilitated workshops
     • Group decision making techniques
     • Questionaries & surveys
     • Observations
     • Benchmarking
   • Process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives

4. 3. Define Scope

   • Process of developing a detailed description of the project and product
     • Tools & techniques
       • Expert judgements
         • Alternatives Generation
       • Product Analysis
       • Outputs
         • Project scope statement
         • Project documentation updates
     • Inputs
       • Scope management plan
       • Project Charter
       • Req. Documentation

5. 4. Create WBS

   • Process of subdividing project deliverables and project work into smaller, more manageable components
   • Inputs
     • Scope Man. plan
     • Project scope stat.
     • Org. Process assets
     • Requirement documentation
   • Tools & techniques
     • Expert judgement
     • Decomposition
       • Technique used for dividing and subdividing the project scope and project deliverables into smaller, more manageable parts.
   • Outputs
     • Scope baseline
       • Project scope statement; WBS; WBS dictionary
     • Project document updates

6. 5. Validate scope

   • Process of formalizing acceptance of the completed project deliverables
   • Inputs
     • P.M Plan
       • Scope management plan
       • Scope baseline
       • Change management plan
     • Requirement documentation
     • Req. Traceability matrix
     • Verified deliverables
   • Tools & techniques
     • Inspection
     • Group decision making techniques
   • Outputs
     • Project documents updates
     • Accepted deliverables
     • Change requests

7. 6. Control scope

   • Inputs
     • P.M plan
     • Req. Documentation
     • Requirements Traceability Matrix
     • Work perf. data
   • Tools & techniques
     • Variance analysis
       • Technique for determining the cause and degree of difference between the baseline and actual performance
   • Outputs
     • Work perf. info
     • Change requests
     • P.M plan updates