Work Breakdown Structure is tree structure division and subdivision of work required to achieve complete project scope.
Key Concepts
Work Package - The work is divided until a manageable level is reached. This end point is called Work Package. Cost, duration, resources can be be accurately defined at Work Package level.
Control Accounts – Control accounts are another point in the hierarchy where management wants to receive updates. Multiple Work packages are assigned to one Control account. However, only one Control Account can be assigned to Work package.
100% Rule – WBS should include 100% of the project scope.
Mutually exclusive – WBS elements should be mutually exclusive to avoid overlapping of work and hence duplication of efforts.
Planned Outcomes – WBS should represent deliverable not the activities to achieve it.
When Should you stop decomposing WBS further?
A question generally arises what should be level of detail at work package level. Here are few guidelines
- 80 Hour Rule – The activities required to produce work package should not exceed 80 hours.
- The activities required for work package should not cross reporting period for the project (weekly, monthly etc).
- Use Common Sense – Do it if it make sense
Few points to keep in mind
- Work Package can be realistically estimated
- Work Package can not be broken down further in practical sense.
- Work package produces measurable deliverable.
- Work package can be outsourced or contracted out.
One Comment
Well said, although there is a lot more to be said. I have a training course available online that is in line with your comments here.
Josh Nankivel