I completely agree with previous comments but I just want to talk about the most important WBS problem and how to fix it. Sometimes teams get caught up in the discussions and end up trying to sequence the work. People add arrows to the WBS, or start to map out the order of tasks on a different sheet, or in a note-taking tool, or even writing dates on the sticky notes as you put them up on the wall. This is a hard one because ultimately the WBS is an input to your project schedule. You will be using it to help you with sequencing tasks… just not right now, so to fix this problem we as a project manager should not let teams talk about task sequencing. This is a facilitation issue. Be strict on the purpose of the session and park any discussions about the order of work.
The WBS lends itself to project efficiency and effectiveness and it is an output of the Scope. To avoid pitfalls of the WBS it is suggested not to make the plan too detailed otherwise the PM will have to micromanage the project, but it can’t be too broad either. The WBS should focus on the deliverables, it shouldn’t be thought of as a task list, and it isn’t a schedule or a replacement for the project plan- again, it’s a visual breakdown of the deliverables.
As most of us know, the WBS is a project management tool designed to arrange project tasks in an orderly fashion. However, one can run into pitfalls if the WBS is not utilized correctly. One potential pitfall is that it may be difficult for project managers to determine the appropriate amount of detail that should be included in the WBS. If not, enough detail is provided, it is possible that one will fail to account for the entire scope of the project, allowing crucial steps to be missed. On the other hand, an overly detailed WBS could lead to an overabundance of tasks requiring a lot of time to document or a situation where the project lead begins to micromanage the process. Neither of these scenarios is preferable and can lead to time and budget overruns (BrightHubPM, 2008).
Essentially WBS is a guide for the project team to ensure that project objectives are accomplished and that deliverables are created and should be approached in a balanced manner (ProjectSmart, 2022).
Can you cite a situation where the WBS was overly ambitious? What were the consequences, if any?
References
BrightHubPM. (2008, July 19). Work breakdown structure pitfalls: Recognizing and avoiding them. https://www.brighthubpm.com/project-planning/2979-work-breakdown-structure-pitfalls-to-avoid/
ProjectSmart. (2022). Work breakdown structure (wbs) purpose, process and pitfalls. Project Smart. https://www.projectsmart.co.uk/work-breakdown-structure/work-breakdown-structure-purpose-process-pitfalls.php
