Scope Baseline
“Scope Baseline” is an output for the process “Create WBS”.
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.
“Scope Baseline” is an input for the process “Define Activities”.
The project WBS, deliverables, constraints, and assumptions documented in the scope baseline are considered explicitly while defining activities.
“Scope Baseline” is an input for the process “Estimate costs”.
The scope baseline is comprised of the following: – Project scope statement. The project scope statement provides the product description, acceptance criteria, key deliverables, project boundaries, assumptions, and constraints about the project.
One basic assumption that needs to be made when estimating project costs is whether the estimates will be limited to direct project costs only or whether the estimates will also include indirect costs. Indirect costs are those costs that cannot be directly traced to a specific project and therefore will be accumulated and allocated equitably over multiple projects by some approved and documented accounting procedure.
One of the most common constraints for many projects is a limited project budget. Examples of other
constraints are required delivery dates, available skilled resources, and organizational policies.
– Work breakdown structure. The WBS provides the relationships among all the components
of the project and the project deliverables.
– WBS dictionary. The WBS dictionary provides detailed information about the deliverables and a description of the work for each component in the WBS required to produce each deliverable.
Additional information that may be found in the scope baseline with contractual and legal implications, such as health, safety, security, performance, environmental, insurance, intellectual property rights, licenses, and permits.
All of this information should be considered when developing the cost estimates.
“Scope Baseline” is an input for the process “Determine budget”.
– Project scope statement. Formal limitations by period for the expenditure of project funds can be mandated by the organization, by agreement, or by other entities such as government
agencies. These funding constraints are reflected in the project scope statement.
– Work breakdown structure. The WBS provides the relationships among all the project
deliverables and their various components.
– WBS dictionary. The WBS dictionary and related detailed statements of work provide an identification of the deliverables and a description of the work in each WBS component required to produce each deliverable.
“Scope Baseline” is an input for the process “Identify risks”.
Uncertainty in project assumptions should be evaluated as potential causes of project risk.
The WBS is a critical input to identifying risks as it facilitates an understanding of the potential risks at both the micro and macro levels. Risks can be identified and subsequently tracked at summary, control account, and/or work package levels.
“Scope Baseline” is an input for the process “Perform Qualitative Risk Analysis “.
Projects using state-of-the-art or first-of-its-kind technology, and highly complex projects, tend to have more uncertainty. This can be evaluated by examining the scope baseline.
This definition was found in the PMBOK V5
Go back to the Glossary or to the Mapping