Chapter 5 - Project Scope Management Flashcards
5.1 Plan Scope Management - Definition:
The process of CREATING a scope management plan that DOCUMENTS how the project scope will be DEFINED, VALIDATED, and CONTROLLED.
5.2 Collect Requirements - Definition:
The process of DETERMINING, DOCUMENTING, and MANAGING stakeholder needs and requirements to MEET project objectives.
5.3 Define Scope - Definition:
The process of DEVELOPING a detailed description of the project and product.
5.4 Create WBS - Definition:
The process of SUBDIVIDING project deliverables and project work into smaller, more manageable components.
5.5 Validate Scope - Definition:
The process of FORMALIZING the ACCEPTANCE of the completed project deliverables.
5.6 Control Scope - Definition:
The process of MONITORING the status of the project and product scope and MANAGING changes to the scope baseline.
5.4.1.1. WBS Input - Scope Management Plan - notes:
The scope management plan specifies how to create the WBS from the detailed project scope statement and how the WBS will be maintained and approved.
5.1.3.1. Plan Scope Management Outputs - Scope Management Plan notes:
The scope management plan is a component of the project or program management plan that describes how the scope will be DEFINED, DEVELOPED, MONITORED, CONTROLLED, and VERIFIED. The scope management plan is a major input into the Develop Project Management Plan process, and the other scope management processes. The components of a scope management plan include:
- Process for preparing a detailed project scope statement.
- Process that enables the creation of the WBS from the detailed project scope statement.
- Process that establishes how the WBS will be maintained and approved.
- Process that specifies how formal acceptance of the completed project deliverables will be obtained.
- Process to control how requests for changes to the detailed project scope statement will be processed.
5.4.1.1 Create WBS - Inputs:
- Scope Management Plan (5.1.3)
- Requirements Documentation (5.2.3)
- Project Scope Statement (5.3.3)
5.4.1.1. WBS Input - Scope Management Plan - notes:
The scope management plan specifies how to create the WBS from the detailed project scope statement and how the WBS will be maintained and approved.
WBS - Definition:
The Work Breakdown Structure (WBS) is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables. The WBS organizes and defines the total scope of the project, and represents the work specified in the current approved project scope statement.
WBS - Definition:
The Work Breakdown Structure (WBS) is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables. The WBS organizes and defines the total scope of the project, and represents the work specified in the current approved project scope statement.
WBS - Definition (cont’):
The planned work described in the WBS is contained within the lowest level of WBS components, which are called work packages. A work package can be used to group the activities where work is scheduled and estimated, monitored, and controlled. In the context of the WBS work refers to work products or deliverables that are the result of activity and not to the activity itself.
5.4.1.1 Create WBS - Inputs:
- Scope Management Plan (5.1.3)
- Requirements Documentation (5.2.3)
- Project Scope Statement (5.3.3)
5.4 WBS - Definition:
The Work Breakdown Structure (WBS) is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables. The WBS organizes and defines the total scope of the project, and represents the work specified in the current approved project scope statement.
5.4 WBS - Definition (cont’):
The planned work described in the WBS is contained within the lowest level of WBS components, which are called work packages. A work package can be used to group the activities where work is scheduled and estimated, monitored, and controlled. In the context of the WBS work refers to work products or deliverables that are the result of activity and not to the activity itself.
5.4.1. Create WBS - Inputs:
- Scope Management Plan (5.1.3)
- Requirements Documentation (5.2.3)
- Project Scope Statement (5.3.3)
5.4.1.1 WBS Input - Scope Management Plan notes:
The Scope Management specifies how to create the WBS from the detailed project scope statement and how the WBS will be maintained.
5.4.1.1 WBS Input - Scope Management Plan notes:
The Scope Management Plan specifies how to create the WBS from the detailed project scope statement and how the WBS will be maintained.
5.4.1.2. Project Scope Statement
The Project Scope Statement describes the work that will be performed and the work that is excluded. It also lists and describes the specific internal or external restrictions or limitations that may affect the execution of the project.
5.4.1.2. Project Scope Statement
The Project Scope Statement describes the work that will be performed and the work that is excluded. It also lists and describes the specific internal or external restrictions or limitations that may affect the execution of the project.
Aka create a list of items to be accomplished by gleaning the deliverables and products from this document.
5.4.1.2. Project Scope Statement
The Project Scope Statement describes the work that will be performed and the work that is excluded. It also lists and describes the specific internal or external restrictions or limitations that may affect the execution of the project.
Aka create a list of items to be accomplished by gleaning the deliverables and products from this document.
5.4.1.2. Project Scope Statement
The Project Scope Statement describes the work that will be performed and the work that is excluded. It also lists and describes the specific internal or external restrictions or limitations that may affect the execution of the project.
Aka create a list of items to be accomplished by gleaning the deliverables and products from this document.
5.4.1.3. Requirements Documentation
Detailed Requirements Documentation is essential for understanding what needs to be produced as the result of the project and what needs to be done to deliver the project and its final products.