top of page

Create WBS

At this point you have collected Stakeholder Requirements (Needs and Expectations) entered them onto your Stakeholder Register, and defined Scope in a written a Project Scope Statement which has been agreed by all your Key Stakeholders with a sign-off. The next step is to create a Work Breakdown Structure (WBS) and a WBS Dictionary.

Project          Scope Statement

Create WBS

Create WBS Dictionary

Scope Baseline consists of all 3 of these documents

​

Click the Icon to see a sample WBS

WBS-Definitions

                            These definitions will be helpful to clarify the process:

Project Scope Statement: The detailed description of the entire scope including project scope and product scope. It includes major deliverables, assumptions, and constraints, and the work required to create those deliverables. It defines which collected requirements will be included and which collected requirements will be excluded from the scope. The Project Scope Statement also includes the measureables (what will be measured and how it will be measured), including success (or acceptance) criteria, against which success will be determined. The Project Scope Statement enables the project team to perform more detailed planning, guides the project team's work during execution, and provides the basis for evaluating whether requests for changes or additional work are contained within or outside the project's boundaries. 

Work Breakdown Structure (WBS): A hierarchical decomposition of the entire scope to be carried out by the project team to accomplish the project objectives and create the project deliverables. It is deliverable based such that if all  items on the WBS are accomplished, all deliverables will be delivered. Likewise items not on the WBS are outside the scope of the project. Items at the smallest part (lowest level) of a WBS are called a work packages; they are deliverables.

 

NOTES about the WBS for your project:

​

1.  It is not decomposed beyond work packages.

2.  It addresses only WHAT and WHERE but not WHY, WHO,       

         WHEN, HOW MUCH (Cost), or HOW.

3.  Your WBS will help you organize the work

4.  It will help you stay on track for delivering 100% of the scope, while

         helping you avoid scope creep 

Decomposition: Technique whereby scope is divided into smaller and smaller, more manageable parts. Each descending level represents an increasingly detailed description of the project work  

Deliverable: Any unique and verifiable product, result, or capability to perform a service, that is produced to complete a process, phase, or project. 

WBS Dictionary: A document that provides detailed deliverable, activity, and other information (scheduling, assigned resources) about each component in the work breakdown structure.

Scope Baseline: The approved version of a Project Scope Statement, Work Breakdown Structure, and its associated WBS Dictionary that can only be changed using formal change control procedures and is used as a basis of comparison to actual results.

 for Creating a WBS:

​

1. The WBS addresses only the WHAT of your project. It should contain no information about the WHO, When, or How.

​

2. 

The approved version of a Project Scope Statement, Work Breakdown Structure, and its associated WBS Dictionary that can only be changed using formal change control procedures and is used as a basis of comparison to actual results.

bottom of page