liveBook · Manning

Work breakdown structure

As explained in Think Like a Software Engineering Manager

A work breakdown structure is a hierarchical decomposition of a project's total scope into progressively smaller work packages and tasks.

When planning a project, start with the full scope of work. A work breakdown structure (WBS) divides that scope into smaller, manageable work packages, typically shown as a tree with the main deliverable at the top and more detailed tasks below. section 10.1.3

Use the breakdown to move toward a plan:

  • Identify the work packages needed to deliver the goal. section 10.1.3
  • Sequence the tasks and add milestones and timelines. WBS maps what work exists; a working-backward plan maps how to reach the goal. section 10.1.3
  • Share the plan so the team understands its responsibilities. section 10.1.3

How Think Like a Software Engineering Manager covers it

How deep it goes
Defines the hierarchy and work packages, but does not walk through constructing a complete WBS.
Examples
Shows a launch timeline with technical design, testing, launch, and retrospective tasks rather than a WBS diagram.
What it assumes
Assumes a project goal, while defining WBS and its work packages from the ground up.
What you can do after
Build it from scratch by dividing project scope into work packages that can seed a working-backward plan.
How it connects
Connects WBS to working-backward planning, Gantt charts, agile frameworks, milestones, and dependencies.
Cover of Think Like a Software Engineering Manager
liveBookmanning.com
Read Think Like a Software Engineering Manager on liveBook Get the book at manning.com

Also explained in

Compare how 2 books explain work breakdown structure →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.