Focusing on a new project is all well and good, but you also must ensure it won’t harm business operations. It happens so easily. Come across any of these? A sponsor executive who doesn’t understand the impact of the project on business processes. A leadership team with a poor grasp…
A WBS (Work Breakdown Structure) is a valuable planning tool which is often overlooked in the rush to create a project schedule. A WBS is a tool defined in the PMBOK. It is a structured decomposition of the entire scope of the project. PRINCE2 also defines a similar planning mechanism as the PBS (Product Breakdown Structure). The purpose of the WBS/PBS is to graphically represent a hierarchy or breakdown of the entire scope of the project, so that it is clear to all involved what is, and what is not, within the scope of the project. It is usual for the WBS/PBS to be represented graphically, often in a hierarchy similar to a hierarchical organisation chart. Project scope is decomposed from the whole project down, into increasingly smaller components to the point where the components are small enough for further detailed planning. The benefits of a WBS are as follows:
- Promotes involvement in the project planning process by subject matter expects
- A good basis for agreement on project scope (stakeholder buy-in)
- A clear visual representation of scope, which will help avoid misunderstandings
- It helps to control scope and avoid later changes (scope creep)
- Identifies external project dependencies at an early stage
- Provides a firm foundation for project scheduling, avoiding replanning work.
Time spent to build and agree upon the WBS is time well spent and will be paid back several times over in time saved as a result of the project team having a clear understanding of the project scope and how its component part fit together.