A work Breakdown Structure is a simple and methodical means of organizing and understanding project scope. The approach enables businesses to take a top-down look at a project and break it into smaller tasks and subtasks that will assist in project completion. It also guides time and cost estimates and schedule development and control. A work breakdown structure (WBS) is a component of project management and systems engineering that breaks a project down into a hierarchy of tasks and deliverables.
Understanding a work breakdown structure
The work breakdown structure diagram illustrates the components of a project vital to its overall success. The final project deliverable is placed at the top of the diagram, with multiple levels below that denoting the systems, sub-systems, components, tasks, subtasks, and work packages critical to project completion. Work packages describe the work required to complete a specific job or process and occupy the lowest level of the WBS diagram.
The number of levels required depends on project complexity. For moderately complex projects, practitioners suggest using three or four levels. More complex projects may require the full complement of six levels. This process of breaking down the project into progressively smaller parts is called decomposition.
Developing a system for the construction of a new aircraft is one example of a complex project with many moving parts. Using a work breakdown structure, the manufacturer may assign one system to aircraft construction and another to pilot training. Within the system tasked with aircraft construction, there may be sub-elements for the airframe, navigation system, and landing gear. Similarly, the airframe construction sub-system itself can be further divided into wings, tail, and fuselage components, and so on.
Creating a work breakdown structure
Following is a very general overview of the steps involved in creating a robust project estimate.
1 – List high-level deliverables
The process starts with defining the project scope. What will the team need to deliver to meet the project end goal?
For example, deliverables for a new company website may include blog content, page design, a sitemap, and front and back end code. Discussing project deliverables as a team is vital because it allows expectations to be set around individual task responsibility.
2 – Segment each deliverable into tasks
These tasks define how the deliverable will be met. In other words, what needs to be done to create the deliverable? What are the task requirements? Are there other project tasks that will assist in its creation? Indeed, are there task interdependencies?
The elements in each level must be mutually exclusive. To avoid duplication and reduce miscommunication, there must be no overlap in deliverables.
3 – Decompose with subtasks
To make the work breakdown structure as detailed as possible, every task must be defined in terms of subtasks. Every level of decomposition must comprise 100% of the level above it and incorporate at least two “child” subtasks.
The process of meticulously ensuring 100% of the scope is captured can be exhaustive, but investing in the approach now means a reduced likelihood of budget blowouts and missed deadlines later.
The company developing a new website may test its navigation menu with ten users. This task can be broken down into subtasks including recruit users, schedule sessions, conduct sessions, compensate users for their time, and write up findings and subsequent recommendations.
The decomposition process should continue until each element can be managed by a single individual or organization.
4 – Format the work breakdown structure and estimate the work
Formatting is usually achieved through Gantt charts because they provide a convenient task hierarchy and are easily referenced. However, a whiteboard or spreadsheet is just as effective.
Once formatted, the team must discuss each task together and estimate a completion time. Summing the estimated completion time for each task will then let the team know whether the project is in or out of the scope defined at the outset.
Key takeaways:
- A work breakdown structure is a component of project management and systems engineering that breaks a project down into a hierarchy of tasks and deliverables
- A work breakdown structure is particularly useful in complex projects requiring diligent and detailed planning. In a process called decomposition, the project is broken down into progressively smaller levels of deliverables and associated tasks.
- The work breakdown structure process can be performed in four steps. The team starts by defining high-level deliverables and then segments them into tasks and sub-tasks. During the final step, the team assigns a time to completion estimate for each task and uses this information to determine whether the project can be delivered within scope.
Connected Business Frameworks
Change is an important and necessary fact of life for all organizations. But change is often unsuccessful because the people within organizations are resistant to change. Change management is a systematic approach to managing the transformation of organizational goals, values, technologies, or processes.
An effective risk management framework is crucial for any organization. The framework endeavors to protect the organization’s capital base and revenue generation capability without hindering growth. A risk management framework (RMF) allows businesses to strike a balance between taking risks and reducing them.
Timeboxing is a simple yet powerful time-management technique for improving productivity. Timeboxing describes the process of proactively scheduling a block of time to spend on a task in the future. It was first described by author James Martin in a book about agile software development.
Herzberg’s two-factor theory argues that certain workplace factors cause job satisfaction while others cause job dissatisfaction. The theory was developed by American psychologist and business management analyst Frederick Herzberg. Until his death in 2000, Herzberg was widely regarded as a pioneering thinker in motivational theory.
The Kepner-Tregoe matrix was created by management consultants Charles H. Kepner and Benjamin B. Tregoe in the 1960s, developed to help businesses navigate the decisions they make daily, the Kepner-Tregoe matrix is a root cause analysis used in organizational decision making.
The ADKAR model is a management tool designed to assist employees and businesses in transitioning through organizational change. To maximize the chances of employees embracing change, the ADKAR model was developed by author and engineer Jeff Hiatt in 2003. The model seeks to guide people through the change process and importantly, ensure that people do not revert to habitual ways of operating after some time has passed.
The CATWOE analysis is a problem-solving strategy that asks businesses to look at an issue from six different perspectives. The CATWOE analysis is an in-depth and holistic approach to problem-solving because it enables businesses to consider all perspectives. This often forces management out of habitual ways of thinking that would otherwise hinder growth and profitability. Most importantly, the CATWOE analysis allows businesses to combine multiple perspectives into a single, unifying solution.
Agile project management (APM) is a strategy that breaks large projects into smaller, more manageable tasks. In the APM methodology, each project is completed in small sections – often referred to as iterations. Each iteration is completed according to its project life cycle, beginning with the initial design and progressing to testing and then quality assurance.
A holacracy is a management strategy and an organizational structure where the power to make important decisions is distributed throughout an organization. It differs from conventional management hierarchies where power is in the hands of a select few. The core principle of a holacracy is self-organization where employees organize into several teams and then work in a self-directed fashion toward a common goal.
The CAGE Distance Framework was developed by management strategist Pankaj Ghemawat as a way for businesses to evaluate the differences between countries when developing international strategies. Therefore, be able to better execute a business strategy at the international level.
First proposed by accounting academic Robert Kaplan, the balanced scorecard is a management system that allows an organization to focus on big-picture strategic goals. The four perspectives of the balanced scorecard include financial, customer, business process, and organizational capacity. From there, according to the balanced scorecard, it’s possible to have a holistic view of the business.
Scrum is a methodology co-created by Ken Schwaber and Jeff Sutherland for effective team collaboration on complex products. Scrum was primarily thought for software development projects to deliver new software capability every 2-4 weeks. It is a sub-group of agile also used in project management to improve startups’ productivity.
Kanban is a lean manufacturing framework first developed by Toyota in the late 1940s. The Kanban framework is a means of visualizing work as it moves through identifying potential bottlenecks. It does that through a process called just-in-time (JIT) manufacturing to optimize engineering processes, speed up manufacturing products, and improve the go-to-market strategy.
The Pomodoro Technique was created by Italian business consultant Francesco Cirillo in the late 1980s. The Pomodoro Technique is a time management system where work is performed in 25-minute intervals.
Andy Grove, helped Intel become among the most valuable companies by 1997. In his years at Intel, he conceived a management and goal-setting system, called OKR, standing for “objectives and key results.” Venture capitalist and early investor in Google, John Doerr, systematized in the book “Measure What Matters.”
Main Free Guides:
- Business Models
- Business Strategy
