Top down approach to divide project deliverables and work into smaller, more manageable components. The WBS organizes and defines the total scope of the project, and represents the work specified in the current approved project scope statement. This is deliverable oriented approach and includes project scope, product scope and project management efforts. This is created with help of the team under the leadership of Project Manager.
Control Account: Used to estimate costs from a higher level. (Not at work package level.)
Notes: Normally, first level of decomposition is project life cycle, but there are other approaches such as major deliverables/ subprojects (outsourcing) at level1. WBS is also used as a communication tool. This can be also be used as a team building activity.
WBS can be used to: evaluate scope change, control scope creep, comms tool, role mapping. It doesn’t show dependencies.
Project Scope Statement
Tools and Techniques:
The WBS can be created with following approaches:
1. Phases of Project Life cycle as first level of decomposition.
2. Major Deliverables as first level of decomposition.
3. Using subprojects which may be developed outside of the team. (Contracts, Outsourcing)
The project team waits till the deliverable or subproject is clarified before WBS can be developed. This technique is referred as ‘rolling wave planning’. Decomposition is not possible that will be accomplished far into the future.
WBS represents all product and project work, including the project management work. The total of the work at the lowest levels must roll up to higher levels so that nothing is left out and no extra work is completed. This is also referred to as a 100% rule.
WBS Dictionary – used to prevent scope creep.
Scope Baseline – Project Scope Statement, WBS and WBS dictionary.
Project Document Updates – such as Requirements Documentation, when approved change requests result from Create WBS process.