Requirements/Scope Management - Part 4. PMBoK Scope Management

Definitions

Product Scope - the features and functions that are to be included in a product or service.

Project Scope - the work required to deliver a product with specified features and functions.

Processes

• Collect Requirements
• Define Scope
• Create WBS
• Verify Scope
• Control Scope

Collect Requirements

Group: Initiating

Inputs:

• Project charter
• Stakeholder register

Tools & Techniques:

• Interviews
• Focus groups
• Facilitated workshops
• Group creativity techniques
• Questionnaires and surveys
• Observations
• Prototypes

Outputs:

• Requirements documentation
• Requirements management plan
• Requirements traceability matrix

Figure 2. Collect Requirements Data Flow Diagram

Define Scope

Group: Planning

Inputs:

• Project charter
• Requirements documentation
• Organizational process assets

Tools & Techniques:

• Expert judgment
• Product analysis
• Alternatives identification
• Facilitated workshops

Outputs:

• Project scope statement
• Project document updates

Scope statement containing of:

• analysis of the product
• list of deliverables
• description of project approach
• list of stakeholders
• estimates
• list of project controls

Figure 3. Define Scope Data Flow Diagram

Create WBS

Group: Planning

Inputs:

• Project scope statement
• Requirements documentation
• Organizational process assets

Tools & Techniques:

• Decomposition

Outputs:

• Work breakdown structure document (WBS)
• WBD dictionary
• Scope baseline
• Project document updates

WBS document hierarchically and graphically represents all work to be done during lifecycle of a project.

Figure 4. Create WBS Data Flow Diagram

Verify Scope

Scope verification is the process of formally accepting the project scope by the stakeholders (sponsor, client, customer, etc).

Group: Controlling

Inputs:

• Project management plan
• Requirements documentation
• Requirements traceability matrix
• Validated deliverables

Tools & Techniques:

• Inspection (measuring, examining, reviewing and testing to determine if results conform to requirements)

Outputs:

• Accepted deliverables
• Change requests
• Project document updates

Figure 5. Verify Scope Data Flow Diagram

Control Scope

Control Scope is the process of controlling changes to project scope.

It includes:

• change management
• replanning
• analysis of deviation from scope
• management of deliverables status

Group: Controlling

Inputs:

• Project management plan
• Work performance information
• Requirements documentation
• Requirements traceability matrix
• Organizational process assets

Tools & Techniques:

• Variance analysis

Outputs:

• Work performance measurements
• Organizational process assets updates
• Change requests
• Project management updates
• Project document updates

Figure 6. Control Scope Data Flow Diagram

References

1. A Guide to the Project Management Body of Knowledge. http://en.wikipedia.org/wiki/A_Guide_to_the_Project_Management_Body_of_Knowledge
2. Project Management Institute. A Guide to the Project Management Body of Knowledge (2008)