PMP Exam Prep – Project Scope Management

Project Scope Management

Introduction

Project Scope Management

  • Includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully.
  • The project team should be aware of the project scope before any work begins.

Project scope management includes 6 processes:

  • Plan scope management
  • Collect requirements
  • define scope
  • create WBS
  • Validate scope
  • Control Scope

Plan Scope Management

  • The process of creating a scope management plan that documents how the project scope will be defined, validated, and controlled.

Key inputs

  • project management plan
  • project charter
  • enterprise environmental factors
  • organizational process assets

Tools and Techniques

  • expert judgement
  • Meetings to develop scope management plan

Key Outputs

  • scope management plan
  • requirements management plan
    • describes how requirements will be analized, documented, and managed.

These outputs become inputs to Collect Requirements Process

Collect Requirements Process

  • determines, documents, and manages stakeholders needs and requirements to meet project objectives.
  • requirements are things that must be done in the project or products that must be provided by the project to meet the needs.

Key Inputs

  • scope management plan
  • requirements management plan
  • stakeholder management plan
  • project charter
  • stakeholder register
    • a project document including the identification, assessment, and classification of project stakeholders.

Tools and Techniques

  • interview important project stakeholders
  • focus groups
  • facilitated workshops
  • group creativity techniques
    • brainstorming
    • mind mapping
  • group decision-making techniques
  • questionnaires and surveys
  • observations
  • prototypes

Key outputs

  • requirements documentation
    • a description of how individual requirements meet the business need for the project.
  • requirements traceability matrix
    • a grid that links product requirements from their origin to the deliverables that satisfy them.

Define Scope Process

  • The process of developing a detailed description of the project and product.

Key Inputs

  • scope management plan
  • project charter
  • requirements documentation
  • organizational process assets

Tools and Techniques

  • expert judgement
  • product analysis
  • alternatives identification
  • facilitated workshops

Key Output

  • Project scope statement
    • description of the project scope, major deliverables, assumptions, and constraints.
  • Project documentation updates

Create WBS

  • Work Breakdown Structure
    • The process of breaking down work into smaller, more manageable units.
  • Work Package
    • the work defined at the lowest level of the work breakdown, structure for which cost and duration can be estimated and managed.

Key Inputs

  • scope management plan
  • project scope statement
  • requirement documentation
  • enterprise environmental factors
  • organizational process assets

Tools and Techniques

  • decomposition
    • a technique used for dividing and subdividing the project scope and deliverables into smaller, more manageable parts
  • expert judgement

Key Outputs

  • scope baseline
    • the approved version of the scope statement, work breakdown structure (WBS), and its associated WBS dictionary, that can be changed only through formal change control process and is used as the basis for comparison
  • Project documents updates

Validate Scope Process

  • the process of formalizing acceptance of the completed deliverables.

Key Inputs

  • Project management plan
  • requirements documentation
  • requirements traceability matrix
  • verified deliverables
  • work performance data

Tools and Techniques

  • inspection
  • group decision-making techniques.

Key Outputs

  • accepted deliverables
  • change requests
  • work performance info
  • project documents updates

Control Scope Process

  • refers to monitoring the status of project and product scope, which helps in managing changes to the scope baseline.

Key Inputs

  • project management plan
  • requirements documentation
  • requirements traceability matrix
  • organizational process assets

Tools and Techniques

  • variance analysis
    • a technique for determining the cause and degree of difference between the baseline and actual performance

Key Outputs

  • work performance information
  • change requests
  • project management plan updates
  • project documentation updates
  • organizational process assets updates
"Material in this blog post are based on the text, Project Management Institute, A Guide to the Project
Management Body of Knowledge (PEMBOK Guide), Fifth Edition, Project Management, Institute, Inc 2013"

"The definitions in this blog post are taken from the Glossarey of the Project Management Institue,
A Guide to the Project Management Body of Knowledge, (PMBOK Guide) - Fifthe Edition,
Project Management Institue, Inc. 2013"

"PMI, PMP, PMBOK are registered marks of the Project Management Institue, Inc"