Work Breakdown Structure (WBS)
What is a Work Breakdown Structure (WBS)?
Work Breakdown Structure (WBS) is a method of breaking down projects into smaller, manageable components for better organisation. It is a hierarchical decomposition of the project or work scope into smaller, more manageable components by organising and structuring the tasks, deliverables, and activities required to complete a project. Work Breakdown Structure (WBS) provides a visual representation of the project's scope, allowing for better planning, scheduling, and resource allocation.
In short:
A WBS is a visual, hierarchical tool used in project management to break down a project into smaller, manageable components.
It visually represents the scope of a project, showing all the tasks and deliverables needed to achieve the project's objectives.
Key Characteristics of a WBS:
Hierarchical: It's structured like a tree, with the project goal at the top and progressively smaller tasks branching out.
Deliverable-Oriented: Each level in the WBS represents a deliverable, a specific product or outcome that needs to be produced.
Inclusive: A well-structured WBS covers all aspects of the project, ensuring nothing is overlooked.
Mutually Exclusive: Tasks should be distinct and not overlap, preventing confusion and duplication.
Collectively Exhaustive: All the tasks in the WBS, when combined, should encompass the entire project scope.
Time-Phased: While the WBS itself doesn't show time, it can be used to create a project schedule by assigning durations to each task.
Benefits of Using a WBS:
Clear Project Scope: Visualises the entire project, reducing the risk of scope creep.
Effective Planning: Provides a foundation for creating detailed project plans, schedules, and budgets.
Improved Communication: Facilitates understanding of the project among team members and stakeholders.
Enhanced Risk Management: Identifies potential risks at each level of the WBS.
Better Control: Enables monitoring and control of project progress by tracking the completion of individual tasks.
Resource Allocation: Helps allocate resources effectively by understanding the resource requirements of each task.
WBS Example 1:
Building a website for a new business.
Project: New Business Website
Phase 1: Planning and Design
Website Requirements Gathering
Design Wireframes
Create Design Mockups
Phase 2: Development
Front-End Development (HTML, CSS, JavaScript)
Back-End Development (Database, Server Setup)
Content Management System (CMS) Integration
Phase 3: Testing and Deployment
Functional Testing
Usability Testing
Security Testing
Deployment to Production Server
WBS Example 2:
Launching a new product.
Project: New Product Launch
Project Initiation
Project Charter Development
Project Team Formation
Risk Assessment
Resource Allocation
Product Development
Product Design and Engineering
Conceptual Design
Detailed Design
Prototyping
Testing and Validation
Manufacturing Process Development
Supplier Selection and Qualification
Production Planning and Scheduling
Quality Assurance and Control
Marketing and Sales
Market Research and Analysis
Target Market Identification
Brand Positioning and Messaging
Marketing Materials Development
Product Brochure
Website
Social Media Campaign
Advertising Campaign
Sales Force Training
Sales Channel Setup
Sales Forecasting and Planning
Launch and Post-Launch Activities
Launch Event Planning and Execution
Inventory Management
Distribution and Logistics
Customer Support Setup
Post-Launch Review and Analysis
Product Performance Monitoring and Improvement
WBS Creation Tips:
Start with the project's overall goal.
Break down the goal into major deliverables.
Continue breaking down deliverables into smaller tasks until they are manageable.
Use clear and concise language for task descriptions.
Involve the entire project team in the WBS creation process.
Visualising the WBS:
WBSs are often represented visually as a tree diagram, making it easier to understand the project structure.
Additional Considerations:
WBS Dictionary: A document that provides detailed descriptions of each WBS element.
WBS Level of Detail: The level of detail depends on the project's complexity and the need for control.
WBS Updates: The WBS should be updated as the project progresses to reflect changes in scope or requirements.
Further Reading
Last updated
