Term Definition
Scope Management process – Plan Scope (Planning)
– Collect Requirements (Planning)
– Define Requirements (Planning)
-Create WBS (Planning)
– Validate Scope (Control & Monitor)
-Control Scope (Control & Monitor)
Scope Management overview – PM plans the work of scope management for project
– Follows plan to determine requirements for project
– PM asks stakeholders what they need from project/product.
-A WBS is then created
– PM confirms deliverables of the project
Product scope Requirements that relate to the product.
Project Scope Requirements that relate to the work required to deliver the product.
Plan Scope Management Develop a plan for how you will plan, manage, control scope & requirements of project.
Collect Requirements – Determine requirements
– Requirements must fit business case & Project Charter
Define Scope Sort & Balance the needs of stakeholders to determine scope.
Create WBS To break scope into smaller workable parts. Each piece should be defined in the WBS dictionary.
Validate Scope Obtain validationfrom client that the completed scope of work is acceptable.
Control Scope Measure scope performance against Scope Management Plan & adjust if necessary.
Scope Outputs 1. Scope Management
2. Requirements Management Plan
Scope Inputs -PMP
-Project Charter
-EEF
-OPA
Tools & Techniques -Expert Judgement
-Meetings
Collecting Requirements -is the process of determining, documenting and managing stakeholder needs and requirements to meet project objectives.
Collecting Requirement Inputs – Scope Management Plan
– Requirements Management Plan
– Stakeholder Management Plan
– Project Charter
– Stakeholder Register
Tools & Techniques -Interviews
-Focus Groups
-Workshops
-Groups Creativity techniques
-Questionnaires/Surveys
-Observations
-Prototypes
-Benchmarking
-Content diagrams
-Document Analysis
Collecting Requirement Outputs Requirements Documentation
Requirements traceability Matrix