Explanation:
5.4.3.1 Scope Baseline
The scope baseline is the approved version of a scope statement, work breakdown structure (WBS), and its associated WBS dictionary, that can be changed only through formal change control procedures and is used as a basis for comparison. It is a component of the project management plan. Components of the scope baseline include:
Project scope statement. The project scope statement includes the description of the project scope, major deliverables, assumptions, and constraints.
WBS. The 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. Each descending level of the WBS represents an increasingly detailed definition of the project work. The WBS is finalized by assigning each work package to a control account and establishing a unique identifier for that work package from a code of accounts. These identifiers provide a structure for hierarchical summation of costs, schedule, and resource information. A control account is a management control point where scope, budget, actual cost, and schedule are integrated and compared to the earned value for performance measurement. Control accounts are placed at selected management points in the WBS. Each control account may include one or more work packages, but each of the work packages should be associated with only one control account. A control account may include one or more planning packages. A planning package is a work breakdown structure component below the control account with known work content but without detailed schedule activities.
WBS dictionary. The WBS dictionary is a document that provides detailed deliverable, activity, and scheduling information about each component in the WBS. The WBS dictionary is a document that supports the WBS. Information in the WBS dictionary may include, but is not limited to:
○ Code of account identifier,
○ Description of work,
○ Assumptions and constraints,
○ Responsible organization,
○ Schedule milestones,
○ Associated schedule activities,
○ Resources required,
○ Cost estimates,
○ Quality requirements,
○ Acceptance criteria,
○ Technical references, and
○ Agreement information
Process: 6.2 Define Activities
Definition: The process of identifying and documenting the specific actions to be performed to produce the project deliverables.
Key Benefit: The key benefit of this process is to break down work packages into activities that provide a basis for estimating, scheduling, executing, monitoring, and controlling the project work.
Inputs
1. Schedule management plan
2. Scope baseline
3. Enterprise environmental factors
4. Organizational process assets
Tools & Techniques
1. Decomposition
2. Rolling wave planning
3. Expert judgment
Outputs
1. Activity list
2. Activity attributes
3. Milestone list