Creating the Work Breakdown Structure

The WBS is a decomposition of the project scope statement. It is a deliverables-oriented document that visualizes all the things the project will create. It is not, and I stress the word not, the activity list. The WBS takes the project scope statement and breaks it down into the deliverables the customer is expecting from the project. It organizes and catalogs the project deliverables.

The smallest item in the WBS, that is the lowest decomposed deliverable, is called the work package. I know what you're thinking (maybe). If the WBS is not about activities then why is it called a Work Breakdown Structure – and why is the smallest element a work package? Good question! When we think of "work" we often think of labor – like I'm working on a report. Work can also be a noun – like the works of Mozart or the works of Picasso. When it comes to the WBS you should think of work as a noun rather than as a series of activities.

The process of creating the WBS should involve the project team and the project's key stakeholders. Yes, the key stakeholders should be involved in creating the WBS. It's important to involve the project stakeholders, as this promotes additional project buy-in and it helps the stakeholders see the depth of deliverables that are included as part of the project.

Comments

[twitter.com/pmstudent]

Absolutely spot-on Joseph! In some cases a gerund is reasonable, although I try to avoid it as well because it can get confused with a function or team.

Josh Nankivel
WBS training instructor
http://WBSCoach.com/7-mistakes