← PMP Scope Management Flashcards

PMP Project Management Professional Exam Study Guide

Key concepts, definitions, and exam tips organized by topic.

25 cards covered

PMP Scope Management Study Guide


Overview

Scope Management is a critical PMP knowledge area that ensures the project includes all the work required — and only the work required — to complete the project successfully. It encompasses six key processes: Plan Scope Management, Collect Requirements, Define Scope, Create WBS, Validate Scope, and Control Scope. Mastery of these processes, their inputs, tools, and outputs is essential for both the PMP exam and real-world project success.


---


Scope Management Processes at a Glance


| Process | Key Output |

|---|---|

| Plan Scope Management | Scope Management Plan |

| Collect Requirements | Requirements Documentation, RTM |

| Define Scope | Project Scope Statement |

| Create WBS | WBS, WBS Dictionary, Scope Baseline |

| Validate Scope | Accepted Deliverables |

| Control Scope | Work Performance Information, Change Requests |


---


Section 1: Scope Planning


Summary

Scope planning establishes the framework for how scope will be managed throughout the entire project. It produces the governing document that all other scope processes follow.


Key Concepts

  • • The Scope Management Plan is the output of Plan Scope Management
  • • It documents the process for defining, validating, and controlling project scope
  • • It defines how the scope statement, WBS, and scope validation procedures will be created
  • • Product scope = features and functions of a product or service
  • • Project scope = the work required to deliver the product with those features

    • Key Terms

  • • Scope Management Plan – Document defining how scope will be defined, validated, and controlled
  • • Product Scope – What the product does (features, functions, characteristics)
  • • Project Scope – The work needed to deliver the product
  • • Product Scope Completion – Occurs when the product meets all documented requirements and specifications

    • Watch Out For ⚠️

    > Product scope vs. project scope is a frequent exam trap. Product scope is measured against requirements; project scope is measured against the project management plan. Know which baseline applies to each.


    ---


    Section 2: Collect Requirements


    Summary

    This process captures, analyzes, and documents stakeholder needs and converts them into measurable requirements that define what must be delivered. The quality of requirements directly impacts project success.


    Key Concepts

  • • Requirements Documentation converts stakeholder needs into measurable, testable requirements
  • • The Requirements Traceability Matrix (RTM) links each requirement back to its origin and forward through delivery, ensuring every requirement adds business value
  • • Requirements must be quantifiable and testable to be useful
  • • Multiple elicitation techniques exist — each suited to different situations

    • Requirements-Gathering Techniques


    | Technique | Description |

    |---|---|

    | Facilitated Workshops (JAD sessions) | Brings diverse stakeholders together to rapidly define cross-functional requirements |

    | Prototyping | Creates a working model/mock-up for stakeholder feedback before finalizing requirements |

    | Context Diagram | Visually depicts the product scope, showing system boundaries and interactions |

    | Interviews | One-on-one conversations with stakeholders |

    | Focus Groups | Guided discussion with pre-qualified stakeholders |

    | Surveys/Questionnaires | Collect data from large groups quickly |


    Key Terms

  • • Requirements Documentation – Captures all stakeholder needs and expectations
  • • Requirements Traceability Matrix (RTM) – Links requirements to their origin and traces them throughout the project lifecycle
  • • Facilitated Workshops – Collaborative sessions (e.g., JAD) to define cross-functional requirements
  • • Prototyping – Presenting an early model to elicit feedback and refine requirements
  • • Context Diagram – Visual depiction of a business system and its interactions, clarifying scope boundaries

    • Watch Out For ⚠️

    > The RTM is NOT just a list of requirements. It traces requirements from origin through delivery and helps ensure nothing is missed or added without authorization. Exam questions may test whether you understand its traceability purpose.


    > Prototyping is iterative. Stakeholders interact with the prototype and provide feedback, which refines requirements — it is not a final product demonstration.


    ---


    Section 3: Define Scope


    Summary

    Define Scope develops a detailed description of the project and product, serving as the foundation for all subsequent scope decisions and documentation.


    Key Components of the Project Scope Statement


    | Component | Description |

    |---|---|

    | Product Scope Description | Features and functions of the product/service |

    | Deliverables | Outputs and results the project will produce |

    | Acceptance Criteria | Conditions that must be met for deliverables to be accepted |

    | Exclusions | Explicitly what is NOT included in the project |

    | Constraints | Limitations that affect how the project is executed |

    | Assumptions | Conditions assumed to be true for planning purposes |


    Key Terms

  • • Project Scope Statement – Detailed description of project and product scope, created during Define Scope
  • • Scope Exclusions – Explicitly stated items NOT included in the project; critical for preventing scope creep
  • • Acceptance Criteria – Measurable conditions deliverables must satisfy to gain customer approval

    • Watch Out For ⚠️

    > Scope exclusions are just as important as inclusions. Failing to document what is excluded invites scope creep. On the exam, if a stakeholder claims something should have been included, check whether it was excluded in the scope statement.


    ---


    Section 4: Create WBS (Work Breakdown Structure)


    Summary

    The WBS hierarchically decomposes the entire project scope into manageable components. It is the backbone of project planning and the foundation of the scope baseline.


    Key Concepts

  • • The WBS is a hierarchical decomposition of total project scope
  • • Decomposition continues until work reaches the work package level
  • • Work packages are the lowest WBS level where work can be scheduled, estimated, monitored, and controlled
  • • The 100% Rule governs WBS completeness
  • • The Scope Baseline = Project Scope Statement + WBS + WBS Dictionary

    • The Scope Baseline Components


    ```

    Scope Baseline

    ├── Project Scope Statement

    ├── WBS

    └── WBS Dictionary

    ```


    Key Terms

  • • Work Breakdown Structure (WBS) – Hierarchical decomposition of total scope into work packages
  • • Work Package – Lowest WBS level; can be scheduled, estimated, monitored, and controlled
  • • WBS Dictionary – Provides detailed information for each WBS component (description, responsible party, milestones, acceptance criteria)
  • • Decomposition – Subdividing deliverables into smaller components until reliably estimable and assignable
  • • 100% Rule – The WBS must capture 100% of scope — no more, no less — at every decomposition level
  • • Scope Baseline – Approved Scope Statement + WBS + WBS Dictionary; used to measure scope performance

    • Watch Out For ⚠️

    > The WBS represents deliverables, NOT activities. A common misconception is that the WBS lists tasks. It lists work products (deliverables). Activities are defined in schedule management.


    > The 100% Rule applies at every level, not just the top level. Each parent node must equal 100% of the work in its child nodes.


    ---


    Section 5: Validate Scope


    Summary

    Validate Scope is the process of obtaining formal acceptance of completed deliverables from the customer or sponsor. It occurs at the end of each phase or iteration.


    Key Concepts

  • • Primary output = Accepted Deliverables (formally signed off by customer/sponsor)
  • • Requires Verified Deliverables as an input (from Control Quality)
  • • Focuses on customer acceptance, not internal quality checking
  • • Occurs after Control Quality confirms correctness

    • Validate Scope vs. Control Quality — Critical Distinction


    | Aspect | Control Quality | Validate Scope |

    |---|---|---|

    | Focus | Correctness of deliverables | Formal acceptance by customer |

    | Performed by | QA/Project Team | Customer/Sponsor |

    | Output | Verified Deliverables | Accepted Deliverables |

    | Sequence | Happens first | Happens second |


    Key Terms

  • • Accepted Deliverables – Primary output of Validate Scope; deliverables formally approved by customer/sponsor
  • • Verified Deliverables – Input to Validate Scope; output of Control Quality confirming deliverables meet quality requirements

    • Watch Out For ⚠️

    > Control Quality comes BEFORE Validate Scope. You verify quality internally first, then seek customer acceptance. Mixing up this sequence is a common exam error.


    ---


    Section 6: Control Scope


    Summary

    Control Scope monitors the status of project scope and manages changes to the scope baseline. It protects the project from uncontrolled scope changes.


    Key Concepts

  • • Uses Variance Analysis to compare actual scope performance against the scope baseline
  • • All scope changes must go through Integrated Change Control before implementation
  • • Distinguishes between scope creep and gold plating
  • • The PM's first response to any change request: evaluate impact, then submit through change control

    • Scope Creep vs. Gold Plating


    | | Scope Creep | Gold Plating |

    |---|---|---|

    | Initiated by | Stakeholders | Project Team |

    | Nature | Uncontrolled expansion of scope | Adding unrequested features/extras |

    | Authorization | Unauthorized | Self-initiated, also unauthorized |

    | Risk | Jeopardizes time, cost, resources | Wastes effort; may not meet real needs |


    Key Terms

  • • Scope Creep – Uncontrolled expansion of project scope without adjustments to time, cost, or resources
  • • Gold Plating – Team-initiated addition of extra features beyond agreed scope
  • • Variance Analysis – Tool comparing actual scope performance against scope baseline to identify deviations
  • • Integrated Change Control – The formal process ALL scope changes must pass through before implementation

    • Watch Out For ⚠️

    > Never implement a scope change without going through Integrated Change Control, even if the customer verbally requests it and it seems minor. The exam will test this discipline repeatedly.


    > Gold plating is NOT a good thing, even if the team is trying to please the customer. It wastes resources, may introduce risk, and bypasses the change control process.


    ---


    Key Relationships & Flow Diagram


    ```

    Plan Scope Management

    ↓

    Collect Requirements → Requirements Documentation + RTM

    ↓

    Define Scope → Project Scope Statement

    ↓

    Create WBS → WBS + WBS Dictionary = SCOPE BASELINE

    ↓

    [Project Execution]

    ↓

    Control Quality → Verified Deliverables

    ↓

    Validate Scope → Accepted Deliverables

    ↑↓

    Control Scope → Manages changes via Integrated Change Control

    ```


    ---


    Master Key Terms List


    | Term | One-Line Definition |

    |---|---|

    | Scope Management Plan | Governs how scope is defined, validated, and controlled |

    | Requirements Documentation | Stakeholder needs converted to measurable requirements |

    | RTM | Traces requirements from origin through delivery |

    | Facilitated Workshops | Collaborative sessions (JAD) for cross-functional requirements |

    | Prototyping | Working model to elicit stakeholder feedback |

    | Context Diagram | Visual of system boundaries and interactions |

    | Project Scope Statement | Detailed description of project and product scope |

    | Scope Exclusions | What is explicitly NOT included in the project |

    | WBS | Hierarchical decomposition of scope into work packages |

    | Work Package | Lowest WBS level; schedulable and estimable |

    | WBS Dictionary | Detailed info for each WBS component |

    | 100% Rule | WBS captures exactly 100% of scope at every level |

    | Decomposition | Breaking deliverables into smaller manageable components |

    | Scope Baseline | Scope Statement + WBS + WBS Dictionary |

    | Verified Deliverables | Output of Control Quality; input to Validate Scope |

    | Accepted Deliverables | Primary output of Validate Scope |

    | Scope Creep | Uncontrolled, stakeholder-driven scope expansion |

    | Gold Plating | Team-initiated addition of unauthorized features |

    | Variance Analysis | Compares actual scope vs. scope baseline |

    | Integrated Change Control | Required process for ALL scope changes |


    ---


    Quick Review Checklist ✅


    Before your exam, confirm you can answer each of these:


  • • [ ] I know the six Scope Management processes in order
  • • [ ] I can distinguish product scope from project scope
  • • [ ] I understand the purpose and contents of the Scope Management Plan
  • • [ ] I know the purpose of the RTM and how it works
  • • [ ] I can name at least four requirements-gathering techniques and when to use each
  • • [ ] I know all six components of the Project Scope Statement
  • • [ ] I understand why scope exclusions are critical
  • • [ ] I can explain the 100% Rule and apply it to WBS scenarios
  • • [ ] I know the difference between a WBS and a WBS Dictionary
  • • [ ] I know the three components of the Scope Baseline
  • • [ ] I can clearly distinguish Validate Scope from Control Quality
  • • [ ] I know that Verified Deliverables → Accepted Deliverables (CQ before VS)
  • • [ ] I can distinguish scope creep from gold plating
  • • [ ] I know that all changes go through Integrated Change Control — no exceptions
  • • [ ] I know that Variance Analysis is the key tool in Control Scope

    • ---


    Good luck on your PMP exam! Remember: in scope management, the key principle is delivering exactly what was agreed upon — no more, no less.

    📝

    Take a Practice Test

    Test yourself with multiple choice questions
    📇

    Study with Flashcards

    Flip through all 25 cards

    Want more study tools?

    Subscribe for $7.99/mo and turn your own notes into personalized flashcards and study guides.

    View Pricing