🧩 Task Breakdown & Work Breakdown Structure

Breaking complex projects into manageable, deliverable pieces.

What is a WBS?

A Work Breakdown Structure is a hierarchical decomposition of the total scope into smaller work packages. Each level adds detail until tasks are actionable.

Breakdown principles

• 100% rule — The WBS must capture 100% of the project scope
• Mutually exclusive — No overlap between work packages
• Outcome-oriented — Focus on deliverables, not activities
• Manageable size — Each task should be estimable (ideally 1-5 days)

Levels

Project
├── Phase / Epic
│   ├── Feature / Milestone
│   │   ├── Task
│   │   └── Task
│   └── Feature / Milestone
│       ├── Task
│       └── Task
└── Phase / Epic

Tips for effective breakdown

• Start from the end: what does "done" look like?
• Use verbs for tasks: "Design", "Build", "Test", "Deploy"
• Identify dependencies between tasks early
• Assign owners at the task level, not the phase level
• If a task feels too big, break it down further

Estimation guidance

Size	Duration	Confidence
Small	< 1 day	High
Medium	1-3 days	Medium-High
Large	3-5 days	Medium
Too big	> 5 days	Break it down