WBS Checklist

Work Breakdown Structure (WBS) check list for use in project planning and scheduling. See also https://www.stakeholdermap.com/plan-project/WBS-checklist.html

Get Started. It's Free
or sign up with your email address
WBS Checklist by Mind Map: WBS Checklist

1. Does it define 100% of the work that will be produced by the project?

2. Does each element represent a deliverable?

3. Does each element have a unique ID that shows its place in the hierarchy e.g. 1.1, 1.2, 1.1.1, 1.1.2?

4. Will project stakeholders be able to understand the project scope from the WBS?

5. Does it capture all external and internal deliverables?

5.1. (including all project management deliverables)

6. Does each level represent 100% of the work required to deliver the parent level?

7. Is the decomposition sufficient that the tasks required to deliver each work package can easily be identified?

7.1. For example

8. Does it gives a clear graphical, textual or tabular breakdown of the scope?

8.1. For example WBS can be:

8.2. Created in Excel

8.3. Be in Mind map format

8.4. have a organisation chart type hierarchy

9. Is a hierarchical structure used?

9.1. For example

10. Does it have a least two levels with at least one level of decomposition?

11. Was it created by those who will be performing the work?

12. Is it being regularly updated as project changes are approved?

13. Can you identify one person who is accountable for each work package?

14. Can you clearly define the acceptance criteria for each work package?

15. Does it allow you to estimate costs accurately?

16. Does the WBS have logical parent elements that can be used in tracking progress?

17. Is the WBS detailed enough to create an Organisational Breakdown Structure and RAM or RACI?

17.1. The relationship between WBS, RACI and OBS

18. Is there an alignment between the WBS and project accounting?

19. Will the WBS support reporting at a team, project, program and portfolio level?

20. Does the WBS align with the size and complexity of the project?

20.1. Is it sufficiently detailed to support planning and control, but not so detailed as to become cumbersome?