- What Is a Work Breakdown Structure?
- What Is Included in a Work Breakdown Structure?
- How to Create a Work Breakdown Structure
- What Are the Different Types of Work Breakdown Structure Diagrams?
- Work Breakdown Structure Example
- WBS Software
- Benefits of WBS Software
- Must-Have Features of WBS Software
- How to Create a WBS in ProjectManager.com
- Work Breakdown Structure Template
- Importance of Work Breakdown Structures in Project Management
- Work Breakdown Structure Best Practices
- Next Steps for Creating a Work Breakdown Structure
- Work Breakdown Structure Resources
What Is a Work Breakdown Structure?
A work breakdown structure (WBS) is a visual, hierarchical and deliverable-oriented deconstruction of a project. It is a helpful diagram for project managers because it allows them to work backwards from the final deliverable of a project and identify all the activities needed to achieve a successful project.
All the steps of a project are outlined in the organizational chart of a work breakdown structure, which makes it an essential project management tool for planning and scheduling. The final deliverable rests on top of the diagram, and the levels below subdivide the project scope to indicate the phases, deliverables and tasks that are needed to complete the project.
Project managers make use of project management software to lay out and execute a work breakdown structure. When used in combination with a Gantt chart that incorporates WBS hierarchies, project management software can be especially effective for planning, scheduling and executing projects.
What Are The Levels of a WBS?
A WBS in project management takes large, complex projects and breaks down the project scope into more manageable pieces to make it easier to plan, schedule and deliver. Tiers of project deliverables and tasks are created to support the planning, execution, and monitoring of projects. There are four main levels of a WBS, which are outlined below:
- The Top Level: The project title or final deliverable.
- Controls Account: The main project phases and deliverables.
- Work Packages: The group of tasks that lead to the controls account level.
- Activities: The tasks needed to complete the work package.
These tiers are found within all the different types of a work breakdown structure.
What Are the Types of WBS?
There are two main types of WBS: deliverable-based, and phase-based. A deliverable-based WBS identifies the project’s deliverables and scope, while the phase-based WBS displays the final deliverable on top, with the level below showing the five phases of a project (initiation, planning, execution, control and closeout).
There are a few uncommon types of work breakdown structures as well:
- A verb-oriented WBS defines the deliverables in terms of actions.
- A noun-oriented WBS defines work in terms of components (this is also called a product breakdown structure).
- A time-phased WBS breaks the project into phases for long-term projects.
A work breakdown structure, clearly, is a very flexible tool. It can take form as a simple numbered list (also known as an outline view), a basic tree diagram or even a Gantt chart. When a Gantt chart is part of a larger project management tool, the WBS can segue into planning, assigning, monitoring and tracking the progress of your team.
Why Use a WBS?
Making a WBS is the first step in developing a project schedule. It defines all the work that needs to be completed (and in what order) to achieve the goals and objectives of the project. By visualizing your project in this manner, you and your resources can collaborate on defining mission critical tasks, their subtasks and the inter-dependencies between them.
A well-constructed WBS helps with important project management processes such as cost estimation, resource allocation, and risk assessment. In addition, a WBS helps avoid common project issues such as missed deadlines, scope creep and cost overrun, among others.
In other words, a work breakdown structure serves as your map through complicated projects. One project may include several phases, or smaller sub-projects—and even those sub-projects can be broken down into deliverables, sub-deliverables and work packages! In doing so, you gain clarity into the details needed to accomplish every aspect of your project.
What Is Included in a Work Breakdown Structure?
A typical work breakdown structure is made up of several key components. They are as follows:
- WBS Dictionary: A document that defines the various elements of the WBS. It’s an important component of a WBS because it allows the project participants and stakeholders to understand the phases, deliverables and work packages with more clarity.
- Task Number & Description: Giving each task a number makes it easy to identify them. A description will help define what the task is, which will provide direction for the team when it’s time to execute it.
- Task Owner: The owner is the person, organization or department who oversees the task from assignment to completion and ensures that it has been properly executed.
- Task Dependency: Some of the tasks on the path to the final deliverable will have to wait until another task is done or started before they can begin. This is called a “task dependency” and requires linking the two dependent tasks together in order to avoid slippage later in the project.
- Cost of Task: Every task is going to have a cost associated with it. You’ll want to note that to keep track of your budget.
- Start, Finish and Estimated Completion of Task: Add the start and finish dates for each task, and estimate the time you have on your schedule to execute it.
- Task Status: The status of the task will show whether it’s assigned or not, in progress, late or complete, which helps with tracking.
How to Create a Work Breakdown Structure
There are five steps to creating a work breakdown structure. These are the big steps, the bird’s-eye view of a WBS, which eventually gets down to the granular level. But it’s good to know the main parts of what is needed to construct a thorough WBS.
- Define the project goals and objectives. Begin with the project charter—the scope, objectives and who is participating in the project—determine what it is and describe it.
- The next level down is the project phases: break the larger project statement of intent into a series of phases that will take it from conception to completion.
- What are your deliverables? List them all and note what is necessary for those deliverables to be deemed successfully delivered (sub-deliverables, work packages, resources, participants, etc.).
- Take your deliverables from above and break them down into every single task and subtask that is necessary to deliver them. Make a list of all those tasks.
- With the tasks now laid out, assign them to the team. Give each team member the tools, resources and authority they need to get the job done.
If you prefer a visual and verbal explanation of this information on work breakdown structures, watch this video.
What Are the Different Types of Work Breakdown Structure Diagrams?
There isn’t just one way to make a WBS. There are, in fact, many different types. Here are a select few:
Work Breakdown Structure List
Also known as an outline view, this is a list of tasks or deliverables, with subtasks. It’s probably the simplest method to make a WBS, which is sometimes all you need.
Work Breakdown Structure Tree Diagram
The most commonly seen version, the tree structure depiction of a WBS is an organizational chart that has all the same elements of the list (phases, deliverables, sub deliverables and work packages) but represents the workflow or progress as defined by a diagrammatic representation. We’ll show an example of this in the next section.
Work Breakdown Structure Spreadsheet
While the classic WBS is a tree diagram, all the parts represented in that graphic can be laid out in a spreadsheet, noting the different phases, tasks or deliverables in columns and rows.
Work Breakdown Structure Gantt Chart
A Gantt chart is both a spreadsheet and a timeline. The Gantt chart is a WBS that can do more than a static spreadsheet or tree diagram. With a dynamic Gantt chart, you can link dependencies, set milestones, even set a baseline. This is the most common version in project management software.
Work Breakdown Structure Example
To help you visualize the WBS, let’s take a look at a project. For our example, we’ll be creating a flowchart variant of a work breakdown structure to guide a commercial building construction project. This is potentially a complex project, but a WBS will take that complexity and boil it down to simpler tasks to make the project manageable.
Study the work breakdown structure example of a construction project below:
At the top of the work breakdown structure is your final deliverable (in this instance, the construction project). Immediately beneath that is the next stage of deliverables, which are the main tasks required to complete the project.
Each of those five project phases—initiation, planning, execution, control and closeout—branch off the main deliverable at the top. Once decided, they are then broken down into a series of tasks. For example, the initiation phase includes site evaluation work and creating the project charter.
These tasks, however, can be further distilled into smaller subtasks. In the execution phase in our construction example, we can look at the interior work. This task is divided into two subtasks, which are installing the plumbing and setting up the electricity.
The WBS, when created as thoroughly as possible, is the roadmap to guide you to completion of what would seem to be a very complicated project. However, when broken down with a WBS, the project suddenly becomes much more manageable.
Related: Construction Plan
Work breakdown structure software is used to outline a project’s final deliverable and define the phases that are necessary to achieve it.
Software facilitates the process in several different ways. Some use a network diagram and others use a Gantt chart. All of them, however, are a visual representation of the project, literally breaking down the various stages and substages needed to assemble the final project deliverable.
Benefits of WBS Software
A work breakdown structure is an essential planning tool. Having software to assist you makes the whole process easier and quicker. It also can connect the work to your larger project planning, execution and more. Here’s what WBS software can do for you:
- Organize Deliverables and Tasks
- Set Schedule Baselines
- Visualize Project Schedule
- List Subtasks and Dependencies
- Estimate Each Task Duration
- Identify Project Phases
Break Tasks Down
Deliverables are important to define, as are the tasks that get you there—but most tasks require being broken down further in order to complete them. That’s where subtasks come in. They’re part of a more complex task, and you want that feature in your WBS software.
Link Dependent Tasks
Not all tasks are the same. Some can’t start or stop until another has started or stopped. These dependent tasks can create a bottleneck later in the project’s execution phase, unless you identify them early. Having a task dependency feature is essential.
Set Task’s Priority and Duration
The point of WBS software is to build a feasible schedule. Therefore, you need features that feed into this process by defining the priority of the task, so you know which phase it goes with; as well as describing the task and estimating how long it will take to complete.
Keep Your Team Working
The WBS sets up your tasks and deliverables, but once the project is in the execution stage, it’s key that you have a way to allocate resources to your team to keep the tasks moving as planned. That includes a feature to make sure their workload is balanced.
Get a High-Level View
Being able to monitor your progress is what keeps your project on schedule. A WBS software sets up the plan and you must have features to maintain it throughout all the phases of the project. Dashboards can give you a view of the landscape across several metrics.
Make Better Decisions
As you move from the planning to the execution stage, you’ll need a reporting feature that can deliver critical project data on progress and performance. This information will feed your decision-making and help you steer the project to a successful conclusion.
How to Create a WBS in ProjectManager.com
The purpose of work breakdown structure software in project management is to organize and define the scope of your project. Using ProjectManager.com’s online Gantt charts to build your WBS is not only more efficient, it dovetails into every other aspect of your project, because of our robust suite of project management features.
Here’s a quick summary of how to create a gantt chart variant of a work breakdown structure in our software. Sign up for a free trial of our software and follow along!
1. Identify Phases for Final Deliverable
There are four phases usually associated with project management. They are initiation, planning, implementation and closure. Each has its array of related tasks that help lead to the final deliverable. The final deliverable is the end product or service generated by the project.
Identify the phases in your project to create more than a mere task list. Set them apart with our milestone feature on the Gantt chart tool. They can also be color coded to better differentiate the phases.
2. List Subtasks, Describe Tasks & Set Task Owner
Subtasks are part of a larger, more complex task. They break up what would otherwise make the task too unruly, but are related enough to the one task that it would not make sense to create a whole new task to define it.
Add summary tasks above the related tasks and indent them. Descriptions can be noted in the task box and further differentiates the task and gives teams direction. Select a team member to own the task and be responsible for its proper execution.
3. Link Dependencies
Task dependencies are tasks that cannot start until another is finished or started. There are four task dependencies, finish to start, start to start, finish to finish and start to finish.
Link tasks that are dependent on one another by dragging one to the other. We link all four types of task dependencies. By identifying these tasks at this stage, you’ll avoid bottlenecks during execution.
4. Set Resources & Costs
Resources are anything that you need to complete the project. They range from the people on your team to materials, supplies and equipment. Knowing your resources and associated costs are what sets and keeps your project within its budget.
Figure out what resources you’ll need to complete each task and estimate how much they’ll cost. Add those figures to the planned cost column on the Gantt chart. This can then be used to compare to actual costs to track your budget in the project.
5 Add Start & End Dates & Estimated Completion
Every task has a start and an end date. The deadline is when the task must be completed. Estimating completion is predicting how long you think the task will take.
Add the date when the task needs to start in the planned start date column and when it should be completed in the planned finished date. There’s also an estimated completion column for the amount of time you plan for the task to take.
6. Track Task Status
Tracking is how to know if a project is performing as planned. When speaking of tasks, tracking tells you multiple things: logged hours, costs, priority, new communications, the percentage complete and how its actual progress compares to your planned progress.
Track the status of each task as it moves through the project cycle. A dropdown menu allows you to tag the task as either unassigned, assigned, in progress or complete, so you are always aware of its actual status in comparison to the plan.
7. Write Notes
Having a section in which to jot down notes is always advisable. While the WBS is thorough, there might be something you need to address that doesn’t fit into its rigid structure.
Write notes to attach to each task or place them in the description or comment section and collect ideas, thoughts and other observations that don’t fit into any of the other columns.
8. Generate Reports
Project reports pull data from the project to illuminate its progress, overall health, costs and more.
Generate a report on your WBS by using our reporting tool. Our reports summarize your project data and allow you to filter the results to show just want you want. Reports can also be shared with stakeholders.
Work Breakdown Structure Template
If you’re not ready to take the plunge and use ProjectManager.com’s work breakdown structure software, but you’re still interested in seeing how using this tool can help you construct a sturdier plan for your next project, don’t worry. We have an intermediate step you can take.
ProjectManager.com is an award-winning project management software that organizes projects and teams. We also have a library of free templates, including a free WBS template, to get you started off right.
If you decide to try out our software, we offer a free 30-day trial. You can upload the project work breakdown structure template into ProjectManager.com, and it automatically creates a new project in our software. Now you can use that template to plan, schedule, monitor and report on your project.
Because our software is cloud-based, all your data is collected and displayed in real time. This makes us different from on-premises project management software like Microsoft Project. We take your WBS and make it more dynamic with our online planning tools to help you define dependencies among the tasks and update these relationships across the project when one task is changed.
If you prefer to see how ProjectManager.com can help translate your WBS into our software, check out the following video.
Importance of Work Breakdown Structures in Project Management
It should be clear why a work breakdown structure is so important to the management of any project. It functions like a to-do list and kick-starts the organizational process by defining the project scope. This tool is a place where you can collect every step you’re going to take on your project to reach the deliverable and create a realistic plan and schedule.
Obviously, the project work breakdown structure comes into play very early in the project’s life cycle. It’s a major part of the planning stage. The project manager is usually the person who, with the project team, makes sure that stakeholders’ expectations are met as they develop the plan. This plan is then sent to those stakeholders for approval. The WBS is the instrument that starts off this whole process.
By using a WBS in the planning stage of your project’s life cycle, you’re ensuring that many of the problems that can sidetrack a project when it’s being executed are avoided. Some of the potential issues that can be reduced by using a WBS include scope creep, missed deadlines, cost overrun and fuzzy requirements. Because the WBS is a visual ladder that connects every step of the production of a deliverable, you stay on track and can even monitor progress more closely.
Work Breakdown Structure Best Practices
As you’re working on your WBS it is helpful to maintain some best practices. Here are some things to keep in mind.
- 100% Rule: This is the most important guiding principle to construct a WBS. It consists in including 100% of the work defined by the project scope, which guarantees that the WBS covers all the deliverables of the project (internal, external and interim). This rule applies to all the levels of the WBS, so the sum of the work at a “child” level must equal the 100% of the work represented by the “parent” level without exception.
- Use Nouns: WBS is about deliverables and the tasks that will lead to your final deliverable. Therefore, you’re dealing more on the what than the how. Verbs are great for action, and should be used in your descriptions, but for clarity, stick to nouns for each of the steps in your WBS.
- Be Thorough: For a WBS to do its job, there must be no holes. Everything is important if it’s part of the course that leads to your final deliverable. To manage that schedule, you need a complete listing of every task, big and small, that takes you there.
- Keep Tasks Mutually Exclusive: This simply means that there’s no reason to break out individual tasks for work that is already part of another task. If the work is covered in a task because it goes together with that task, then you don’t need to make it a separate task.
- Go Just Deep Enough: You can get crazy with subtasks on your WBS. The WBS has to be detailed, but not so deep that it becomes confusing. Ideally, think maybe three or five at most levels.
Next Steps for Creating a Work Breakdown Structure
The work breakdown structure is a great way to take the chaos of a project and reign it in. You start with the big picture and then drill down to the details. Once you have a WBS for your project, you need to plan, execute and monitor its progress. That’s where ProjectManager.com comes in. As shown above in the step-by-step guide, our online Gantt charts help project managers plan the project schedule.
Teams work differently than project managers, though; which is why we offer multiple project views. Our kanban boards visualize workflow and task lists for daily work. Teams can keep track of what tasks are high priority, and focus only on where resources match capacity. Managers get transparency into the process and can keep things moving smoothly.
You’ll need to keep track of your progress, so you can avoid scope creep, but that can prove difficult without the right tools. ProjectManager.com has robust, real-time dashboards that allow a high-level view of the project. Easily monitor several key metrics across all of your projects with automatically updating graphs and charts.
All our tools are geared to making your project more efficient and effective. See for yourself by starting your free 30-day trial of our software.
Work Breakdown Structure Resources
See Why Teams Love ProjectManager.com
Start managing your work your way.
2,000,000+ projects planned, by companies including