- a WBS does NOT include activities and tasks; these are planned out from the work packages within the schedule
- it is up to the team how each deliverable is broken down
- at the second level and below, identify everything (unique deliverables) needed to complete the project
- the work packages on the WBS should reflect all deliverables for the entire scope of the project
- Apply the 100% Rule
- A WBS must represent and ultimately capture all efforts devoted to that project and, just as importantly, none that are not devoted to the project
- ensure the work packages are numbered on the WBS for easy reference
- the WBS does not reflect priorities or order of execution; this will be reflected within the schedule
- create a supplemental WBS dictionary to provide more information about the work packages such as completion criteria, complexity, dependencies, estimated effort, and owner to facilitate the creation of a schedule
- if using MS Project to create the schedule, use the WBS field to record the work package number for reference
- results can be documented in either a tabular or graphical format using the preferred WBS documentation tool
- the top level represents the final deliverable or project
- effort of work within each work package should be between 1 to 14 days
- all elements of the WBS don’t need to be defined to the same level
- work packages should be independent of other work packages
- work packages are unique and should not be duplicated across the WBS
- a WBS must capture all efforts devoted to the project and none that are not devoted to the project
- the WBS should also include project management deliverables and work