Version 1.0
Revision History
Date | Rev | Author | Description | MM/DD/YY | 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
Table of Contents 1. Purpose 4 2. Scope Management Framework 4 3. Scope Management Process 5 4. Scope Management Approach 5 5. Roles and Responsibilities 6 Appendix A: Sample Scope Management Plan 7
Table of Tables Table 1: Process Summary 5 Table 2: Scope Management Roles and Responsibilities 8 Table 3: WBS Dictionary 10
Table of Figures Figure 1: Process Flow Chart 6 Figure 2: Work Breakdown Structure 9
Purpose
Scope Management is the process to ensure that the project defines the scope of the required work as well as defines out-of scope work not necessary to support the project. The Scope Management Plan details how the project scope will be defined, developed, and verified. The Scope Management Plan clearly defines who is responsible for managing the projects’ scope and acts as a guide for managing and controlling the scope.
Scope Management Framework
Project Scope Management follows a five step process: collect requirements, define scope, create a work breakdown structure (WBS), verify scope, and control scope.
1. Collect Requirements – Collecting requirements defines and documents requirements needed to meet all project objectives. To begin collecting requirements the project team should leverage the project charter and stakeholder list. Starting with the inputs, the team should identify requirements, research details to accomplish the requirements, detail the requirements, and determine measurable criteria to monitor the requirements. Refer to the Requirements Traceability Framework. Document the tools and techniques used to