100%(1)1 out of 1 people found this document helpful
This preview shows page 3 - 5 out of 5 pages.
manageable elements. These elements are further subdivided until the deliverables are
specific enough to support the integration of planning, executing, monitoring and controlling, and closing process group activities. The resulting collection of elements that define the total scope of the project is called the work breakdown structure (WBS). In defining project scope, there are six key processes that a project manager must understand and complete to ensure successful implementation and completion of the project. The six processes are outlined below: 1. Plan Scope Management: plan. This process defines how the scope will be defined, validated, and controlled. 2. Collect Requirements: This process defines the activities needed to determine the features and functions of the final project deliverable that meets the needs and expectations of the stakeholder community. 3. Define Scope: This process refines the project scope by creating a scope statement. It leverages the project charter and plan scope management process to obtain additional information about the final deliverable of the project. 4. Create WBS: This process focuses on defining the work of the project. It breaks down the scope statement into work packages that the project team must execute in order to achieve the project objectives. The WBS is usually demonstrated as a deliverable-oriented hierarchical structure. 5. Validate Scope: This process focuses on getting the formal acceptance of completed deliverables from the stakeholder community. This process confirms that work has been completed correctly and meets the needs and expectations of project stakeholders. 6. Control Scope: This process monitors the status of both project and product requirements. It also includes managing changes to project requirements and the scope baseline. The scope baseline is the conglomeration of the approved version of the scope statement, WBS, and WBS dictionary. It can be changed only through formal project change control procedures.
Reference Project Management Institute (2013). A guide to the project management body of knowledge . Newton Square, PA: Project Management Institute, Inc.