ConceptReviewed
Project (Work Breakdown Structure)
Name variants
- English
- Project (Work Breakdown Structure)
- Katakana
- プロジェクト
Quality / Updated / COI
- Quality
- Reviewed
- Updated
- Source
- Citations & Trust
- COI
- none
TL;DR
A WBS decomposes deliverables into a hierarchy of work.It aligns stakeholders and provides a shared basis for planning and execution.
Definition
The Work Breakdown Structure (WBS) breaks deliverables into a hierarchical set of manageable components to clarify scope and ownership.It links objectives, scope, resources, and time, serving as a baseline for alignment and change control.
Decision impact
- Clear scope and objectives align priorities and reduce rework in decisions.
- Visible dependencies make schedule adjustments and resource trade-offs faster.
- Change and risk impacts can be assessed early, improving alignment.
Key takeaways
- Define deliverables and acceptance criteria to prevent scope drift.
- Record assumptions, constraints, and exclusions for shared expectations.
- Link dependencies to owners and dates to ease coordination.
- Review progress against the baseline, not just activity.
- Log changes with reasons and impacts to maintain transparency.
Misconceptions
- Plans are not immutable; controlled changes are expected.
- More detail is not always better if it raises maintenance cost.
- Documentation alone does not deliver results without execution.
Worked example
Example: Split a website project into requirements, design, development, testing, and launch, then into features.When change requests arise, assess impact and renegotiate priorities with stakeholders.Review progress weekly and agree on mitigation if delays appear.Document major changes and approvals for traceability.
Citations & Trust
- Project Management (Open Textbook Library)