WBS (Work Breakdown Structure)
Short Tip: An artifact in a hierarchical structure that lists a product’s releases.
What is it?
It is a hierarchical diagram showing the releases for a given product. In a predictive model, the WBS describes the total scope to be built in a level of detail that allows more accurate estimates in other areas, such as activities, human and material resources, costs and deadlines.
Why use it?
The WBS is a common artifact in predictive project management. Its design defines the scope of the project.
How to use it?
The WBS should be designed with the Development Team. If a Story Map has been made for the product, the WBS is usually designed subsequently.
- Based on the product’s view and the Support Canvas (Project-Value Canvas or Lean Canvas) and the Story Map (if there is one), identify the main releases required for the product;
- Break down those releases into smaller units until you reach the work package level;
- Make sure the work package corresponds to a task that is inferior to a cycle. Otherwise, break it down into smaller units. A work package typically corresponds to 8-80 hours’ work.
- Create a basic description of the WBS in a dictionary format, including details of the release.