Skip to content
Tutorials Center
My learning

Topics

Lesson 13 of 41 ยท Scope, Time and Cost

Work Breakdown Structure (WBS)

Learn how to build a work breakdown structure: decomposing scope into work packages, the 100 percent rule, WBS dictionary, levels of detail and common mistakes, with a runnable roll-up.

A work breakdown structure (WBS) breaks the total scope of a project into smaller and smaller pieces until each piece is small enough to estimate, assign and track. It is a hierarchical picture of deliverables, not of the order in which work is done. Once you have a WBS, estimating cost, building a schedule and assigning responsibility all become manageable.

Why use a WBS

  • It makes sure all the scope is included (and nothing else).
  • Small pieces are easier to estimate than big vague ones.
  • Each piece can have a clear owner.
  • It is the foundation for the schedule, budget, risk and reporting.
  • It gives everyone a shared view of "what the project is".

The structure

At the top is the project (level 0). Beneath are major deliverables or phases (level 1), then sub-deliverables, down to work packages, the lowest level, which are estimated and assigned. A work package is typically a chunk of work that one person or team can finish in roughly 8 to 80 hours or one to two weeks, though the rule of thumb depends on the project.

flowchart TB
    P["Online store project"] --> A["1 Management"]
    P --> B["2 Design"]
    P --> C["3 Build"]
    P --> D["4 Test and launch"]
    B --> B1["2.1 Wireframes"]
    B --> B2["2.2 Visual design"]
    C --> C1["3.1 Catalogue"]
    C --> C2["3.2 Cart and checkout"]
    C --> C3["3.3 Admin panel"]
    D --> D1["4.1 System test"]
    D --> D2["4.2 Go-live"]

A deliverable-based WBS. The leaves are work packages.

Numbering

Give each element a unique ID: 1, 1.1, 1.2, 2, 2.1... The numbers show the hierarchy and appear in schedules, budgets and reports.

The 100 percent rule

The WBS must include 100% of the work defined by the scope: everything in, nothing outside it. At each level, the children together equal the parent. If "Build" has three children, those three cover all of "Build". The rule also applies to the project management work itself; include a "Management" branch.

Ways to organise it

  • By deliverable (recommended): nouns such as "Catalogue", "Admin panel".
  • By phase: Design, Build, Test (common and simple, but can hide deliverables).
  • By area or team: front end, back end.

Prefer nouns for deliverables over verbs for tasks. "Login page" belongs in a WBS; "Write code for login page" belongs in the activity list that comes next, in Activities and Resources.

The WBS dictionary

The WBS dictionary describes each work package: ID, description, owner, deliverable, acceptance criteria, assumptions, effort and cost estimate, and dependencies. It stops two people from interpreting "Reporting" differently.

A WBS as data

You can store a WBS as nested data and roll up costs automatically.

Python Roll up a WBS

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Checking work package size

Python Flag work packages that are too big

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

How to build one

  1. Start with the scope statement and deliverables.
  2. Gather the team; a WBS built with the people who do the work is more complete.
  3. Write each deliverable on a note (or use a tool); group and break down.
  4. Keep decomposing until pieces can be estimated and owned.
  5. Check the 100% rule and number everything.
  6. Write the WBS dictionary entries.
  7. Review with stakeholders and baseline it with the scope statement.

Common mistakes

  • Listing tasks and their order instead of deliverables.
  • Going too shallow (work packages that are weeks of unclear work) or too deep (hundreds of 1-hour boxes that are tedious to maintain).
  • Forgetting management, testing, training or data migration.
  • Mixing two ways of grouping at one level.
  • Treating it as finished; update through change control.

For software projects, a WBS may also be created from a feature list, or each feature split into design, build, test and document packages. Agile teams keep a product backlog instead, which serves a similar purpose but evolves continuously.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does the 100 percent rule require?

    Children at each level add up to the parent: complete and without extras.
  2. 2. A work package is...

    Work packages are the leaf items you estimate, assign and track.
  3. 3. A WBS is organized by...

    It shows what is delivered; sequencing comes later in the schedule.
  4. 4. The WBS dictionary contains...

    It defines each package: owner, deliverable, acceptance criteria and estimates.

Summary

  • A WBS decomposes scope into deliverables down to estimable work packages.
  • Follow the 100% rule; number elements and describe them in a WBS dictionary.
  • Use deliverable nouns and include management work.
  • The WBS feeds activity lists, estimates, schedules and budgets.

Next: Activities and Resources