Making Sense of the WBS

  Work Breakdown Structures (WBS)   ProjectsAtWork  

A work breakdown structure is a critical project-planning tool. Why is it so misused and misunderstood?

Dazed and confused. That's how some project managers feel when faced with the task of creating a work breakdown structure (WBS). A WBS is supposed to tell the story of how the project will run and how the deliverables will be defined. But, according to Bill Duncan, principal with Project Management Partners in  Lexington, Mass., the WBS is more often misapplied and misused by project managers than used correctly.

The WBS can be the most critical part of the project planning process, but if designed poorly, it could undermine your success in planning and executing a project. Before you get frustrated with your next WBS, consider these empowering and enlightening guidelines.

Avoid Too Many To-Do Lists

The main problem many project managers face in designing a WBS is laying out too many tasks. The task-focused process often leads to unnecessary tasks, a waste of resources and an inefficient use of customer investments. "Don't get lost in the weeds," warns Kevin Aguanno, PMP, MAPM, principal and senior project manager in the Business Innovation Services division at IBM Canada Ltd. The WBS should not read like a daily 'to-do' list, he says.

Instead, Aguanno says, follow a product-focused process …

Please log in or sign up below to read the rest of the article.