10:39
Creating a Work Breakdown Structure (WBS) in Project Management
Terrena Hooper
Overview
This video explains the Work Breakdown Structure (WBS) as a fundamental project management tool for defining project scope. It details how a WBS decomposes a project into smaller, manageable components, organized hierarchically. The video demonstrates creating a WBS using a template, emphasizing clear naming conventions and coding for communication. It also distinguishes between two primary WBS organizational styles: process-based and product-based, advising learners to choose the style that best suits their project's nature and stakeholder understanding.
How was this?
Save this permanently with flashcards, quizzes, and AI chat
Chapters
- A WBS is a project management tool used to define the project's scope by breaking it down into smaller, hierarchical components.
- If a task is not included in the WBS, it is likely to be missed during project execution.
- The WBS serves as a communication tool with stakeholders to confirm the project scope is correctly defined.
- Work packages are the lowest level of the WBS and represent specific groupings of work.
Understanding the WBS is crucial because it ensures all necessary project work is identified and accounted for, preventing scope creep and miscommunication.
An example WBS for a 'Compliance Training' project includes top-level deliverables like 'Update Training Modules,' 'Staff Training,' and 'Evaluate and Close,' with sub-packages like 'Review and update existing modules' under 'Update Training Modules.'
- Start by naming the project clearly.
- Identify the main deliverables or high-level components of the project.
- Decompose each main deliverable into smaller work packages or tasks.
- Assign unique codes (e.g., 1.0, 1.1, 1.2) to each deliverable and work package for easy reference and communication.
- Ensure work package names are concise and distinct to avoid confusion.
Following a structured process for WBS creation ensures that the project is systematically broken down, making it easier to plan, assign, and track individual tasks.
For an 'Employee Engagement Survey 2020' project, the WBS might start with 'Develop Survey' (1.0), broken down into 'Consultation' (1.1), 'Build Draft Survey' (1.2), and 'Finalize Survey' (1.3).
- WBS can be organized based on a process flow (sequential steps) or by product/deliverable (distinct outputs).
- A process-style WBS follows a logical sequence where one step must be completed before the next (e.g., develop, implement, analyze).
- A product-style WBS groups work by the specific items or deliverables being created, which can often be worked on concurrently (e.g., bathroom, kitchen, dining room in a house renovation).
- The choice between process and product style depends on the project's nature and what makes the most sense for planning and execution.
- The primary goal is to create a WBS that is logical, easy to understand for stakeholders, and accurately reflects the project scope.
Selecting the appropriate organizational style for your WBS impacts how the project is perceived, planned, and executed, influencing dependencies and team assignments.
A house renovation project might use a product-style WBS with categories like 'Bathroom,' 'Kitchen,' and 'Dining Room,' whereas a software development project might use a process-style WBS like 'Design,' 'Develop,' 'Test,' and 'Deploy.'
Key takeaways
- The WBS is the definitive tool for defining and controlling project scope.
- Decomposition is key: break large projects into smaller, manageable work packages.
- Clear, concise, and unique naming of WBS elements is essential for effective communication.
- Hierarchical coding in a WBS provides structure and aids in referencing specific work items.
- The WBS should be developed early in the project lifecycle to guide subsequent planning.
- Choose a WBS organizational style (process or product) that best represents your project's structure and facilitates understanding.
- A well-constructed WBS ensures that all project work is identified and accounted for, preventing tasks from being overlooked.
Key terms
Work Breakdown Structure (WBS)Project ManagementScopeDeliverablesWork PackagesDecompositionHierarchical StructureCodingProcess Style WBSProduct Style WBS
Test your understanding
- What is the primary purpose of a Work Breakdown Structure in project management?
- How does a WBS help prevent scope creep and ensure all project tasks are identified?
- What are the key differences between a process-style WBS and a product-style WBS?
- Why is it important to use clear and unique names for elements within a WBS?
- How can hierarchical coding in a WBS improve project communication and organization?