Scope Management Flashcards
Product Scope
Requirements for the final product
Project Scope
work the project team will do to deliver the product of the project, including the product scope
Inputs: Plan Scope Management
- Project Charter
- PM Plan
- EEFs
- OPAs
Outputs: Plan Scope Management
- Scope Management Plan
- Requirements Management Plan
Scope Management Plan
- how to achieve scope
- what tools to use to plan
- how to create the WBS
- how scope will be managed and controlled
- how to obtain acceptance of deliverables
Requirements Management Plan
aka business analysis plan
outlines how requirements are analyzed, prioritized, managed, and tracked
Types of Requirements
- how the work is planned and managed
- capabilities for product
- stakeholder requirements (from stakeholder register)
- quality measures
- business procedures (i.e. reporting of expenses)
- legal or ethical complaince
- project management procedures
Inputs: Collect Requirements
- Project charter
- PM Plan
- Project docs
- Business docs
- Agreements
- EEFs
- OPAs
Outputs: Collect Requirements
- Requirements documentation (including acceptance criteria)
- Requirements traceability matrix
Affinity diagrams
Groups ideas for requirements by similarities; aid in determining whether all areas of scope have been identified
Also used for risks.
Nominal Group Technique
- question or issue is posed
- all meeting particiapants write down and share their ideas
- group discussion
- ideas ranked
Delphi Technique
requirements are collected anonymously from SMEs (to avoid stakeholders influencing each other)
Facilitation
concensus-based approach that brings stakeholders with different perspectives to talk about the product & define reqirements.
user stories may be developed through facilitation
Quality Functional Deployment
type of facilitation, aka voice of the customer
Context Diagrams
shows boundaries of scope by highlighting the product and its interfaces with people, processes or systems
Requirement Traceability Matrix
links requirements to the objectives to ensure strategic goals are accomplished
(may also link to stakeholders and origin of requirement)
Inputs: Define Scope
- Project Charter
- PM Plan
- Project docs
- EEFs
- OPAs
Outputs: Define Scope
- Project Scope Statement
- Project docs updates
Project Scope Statement
douments the characteristics and boundaries of the project and its associated products, results, and services in addition to the acceptance criteria.
Components of Project Scope Statement
Components may vary depending on project approach.
- product scope
- detailed list of deliverables*
- acceptance criteria
- exclusions
- constraints
- assumptions
* must be in all scope statements
Scope Baseline
Scope statement, WBS, WBS dictionary
Inputs: Create WBS
- PM Plan
- Project Docs
- EEFs
- OPAs
Outputs: Create WBS
- Scope Baseline
- Project docs update
Levels of WBS
Project
Control Accounts
Work Packages
Note: Work Packages should be work products or deliverables, NOT activities.
Difference between task and activity
activity: particular piece of work scheduled for the project
tasks: smaller components of work that make up an activity
WBS
a graphical picture of the hierarchy of a porject
identifies all deliverables to be completed
does not show dependencies
PM uses for WBS
- to determine appropriateness of scope-related change request
- evaluate impact of changes that relate to scope
- control scope creep
- communicatins tool
- onboarding of team members
WBS Dictionary
provides a desription of the work to be done for each WBS work package + acceptance criteria for each deliverable
Inputs: Validate Scope
- PM Plan
- Project docs
- Verified Deliverables
- Work Performance Data
Outputs: Validate Scope
- Accepted deliverables
- Change requests
- Work Performance Information
- Project docs updates
Validate Scope
process where deliverables are formally inspected and accepted by the customer or sponsor.
occurs immediately after Control Quality
What is the difference between acceptance in Validate Scope & Close Project or Phase?
Validate Scope = (interim) deliverables acceptance
Close Project or Phase = final project acceptance
Inputs: Control Scope
- PM plan
- Project docs
- Work Performance Data
- OPAs
Outputs: Control Scope
- Work Performance Information
- Change Requests
- PM Plan updates
- Project docs updates
- OPAs updates
What process includes testing of interim deliverables?
Control Scope
