How to develop a work breakdown structure (WBS)
Wondering How the WBS differs from Requirements, Scope of Work and Project Plan?
You are not alone! The WBS process is a component of all three, let’s review its key elements and purpose.
WBS includes subdividing project deliverables and project work into more manageable components.
Inputs
Project management plan (scope management section).
Project documents (project scope statement, requirements document).
Enterprise environmental factors (industry specific WBS standards).
Organizational process assets (policies, procedures, previous project files).
Tool & Techniques
Expert Judgment.
Decomposition – dividing and subdividing project scope and deliverables into smaller parts.
Outputs
Scope baseline.
Project documents updates (assumption log, requirements documentation).
Use of Decomposition Method to Create an Appropriate WBS
Structure WBS as an outline, an organizational chart, or other methods that identifies a hierarchical breakdown.
Define the outline of the entire project.
Identify the main deliverables below the finished project.
Divide each deliverable into sub-tasks until the last level can be measurable (in terms of budget and resources).
Follow 100% rule – the sum of the “child tasks” must equal to the work the “parent tasks”.
Use exclusive units and define by deliverables.
Example 100% rule
Example WBS
Jumpstart your WBS using software like Lucidchart, MatchWare, or Edraw to reduce time!
https://www.appvizer.com/operations/bpm/lucidchart
https://www.matchware.com/wbs-software
https://www.edrawsoft.com/work-breakdown-structure-software.html?msclkid=2cf28b7480571f69800ad44f84a