4.2.1: Step 2 – Build the Work Breakdown Structure (WBS)

The Work Breakdown Structure (WBS) is the foundation of all detailed project planning. It is the first operational artifact that converts strategy and structure (from Milestone 2) into work units that can be scheduled, estimated, resourced, and managed.

The WBS answers the question:
“What exactly must be done—broken into components small enough to plan and track?”

This section provides a highly detailed, replicable process for building a professional-level WBS.

🚀 Why the WBS Comes First

Before you can estimate effort, determine dependencies, or build a schedule, you must:

• Understand the full scope of work

• Break the project into manageable work packages

• Ensure all deliverables and commitments are represented

• Provide a structure the team can use to assign tasks and track progress

Without a good WBS:

• Your estimates will be wrong

• Your dependencies will be unclear

• Your milestones will be misaligned

• Your schedule will not reflect reality

A good WBS is not optional—it is the backbone of execution planning.

🧭 Step-by-Step Instructions for Building the WBS

Below are the detailed steps a student (or practitioner) should follow.

STEP 1.1 – Revisit the Scope, Deliverables, and Approach From Milestone 2

Before breaking anything down:

1. Reopen Section 1: Scope

2. Reopen Section 4: Deliverables

3. Reopen Section 3: Project Approach

Ask:

• What outcomes must we produce?

• What phases did we define?

• What are the major deliverables in each phase?

Everything in your WBS must stem from these three documents.
No new tasks or deliverables should appear unless justified.

OUTPUT:
A list of all high-level deliverables/phases to be represented in the WBS.

STEP 1.2 – Identify Level 1 WBS Components

Level 1 represents the highest-level project groupings, usually aligned to:

• Project phases

• Major deliverables

• Workstreams

• Functional areas

• Project approach steps

Typical Level 1 categories:

• 1.0 Planning Activities

• 2.0 Design

• 3.0 Build/Execution

• 4.0 Testing/Validation

• 5.0 Deployment/Transition

• 6.0 Project Management & Governance

Choose Level 1 headings that reflect your project.

OUTPUT:
A list of Level 1 components that represent the entire project scope at a glance.

STEP 1.3 – Break Level 1 Items Into Level 2 Work Packages

Level 2 items should represent major work packages inside each phase.

Example for “2.0 Design”:

• 2.1 Requirements Documentation

• 2.2 Architecture Modeling

• 2.3 Interface Prototyping

• 2.4 Integration Planning

Example for “3.0 Execution/Build”:

• 3.1 Module A Construction

• 3.2 Module B Construction

• 3.3 Data Setup

• 3.4 Configuration & Customization

Work Packages should:

• Be deliverable-focused

• Be large enough to represent meaningful work

• Be small enough to break into tasks

OUTPUT:
A complete list of Level 2 work packages under each Level 1 heading.

STEP 1.4 – Break Level 2 Items Into Level 3 Tasks

Level 3 is where work becomes actionable.
These are the tasks you will later:

• Estimate

• Sequence

• Assign

• Track

Guidelines for Level 3 tasks:

• Each task should be 3–40 hours of work

• Each must support a Level 2 deliverable

• Use verb + object naming (e.g., “Document workflow inputs”)

• Avoid overly broad tasks (“Do analysis”) or overly small tasks (“Email sponsor”)

Example for “2.1 Requirements Documentation”:

• 2.1.1 Conduct stakeholder interviews

• 2.1.2 Synthesize requirements

• 2.1.3 Draft requirements document

• 2.1.4 Review and update based on feedback

OUTPUT:
3–8 Level 3 tasks for each Level 2 work package.

STEP 1.5 – Validate That Your WBS Covers 100% of the Scope

This is called the 100% Rule:

The WBS must contain 100% of the work required to complete the project, no more and no less.

Checklist:

• Does every deliverable from Milestone 2 appear in the WBS?

• Is anything missing?

• Is anything added that wasn’t scoped?

• Is project management included as a work package?

OUTPUT:
A WBS that reflects every deliverable defined earlier.

STEP 1.6 – Apply WBS Numbering and Formatting

Use standard hierarchical numbering:

• 1.0

  • 1.1

    • 1.1.1

  • 1.2

    • 1.2.1

Rules:

• Level 1 always ends with “.0”

• Children increment (“1.1”, “1.2”, “1.3”)

• Never skip numbers

• Use consistent indentation

This creates easy traceability during scheduling and estimation.

OUTPUT:
A clean, structured, numbered WBS.

STEP 1.7 – Review for Clarity, Independence, and Non-Overlap

Every WBS task must be:

• Mutually exclusive (no overlap)

• Collectively exhaustive (complete coverage)

• Understandable by someone outside the team

Ask:

• Can someone read this WBS and understand the work without explanation?

• Does any task duplicate another?

• Are any tasks so vague they can’t be estimated?

If yes → revise.

OUTPUT:
A professionally structured WBS that is ready for estimation and scheduling.

STEP 1.8 – Produce the Final WBS for Submission

Final WBS should be:

• Cleanly formatted

• Includes Level 1, Level 2, Level 3

• Uses clear naming

• Traceable to scope and deliverables

• Ready for use in Milestone 3 Steps 2–4

Allowed formats:

• Table

• Outline

• Hierarchical list (most common)

• Numbered work packages

OUTPUT:
The final WBS section of your Milestone 3 submission.

📄 WBS Template (Plain Text Version)

1.0 Project Planning Activities
    1.1 Stakeholder Engagement
        1.1.1 Identify stakeholders
        1.1.2 Schedule interviews
        1.1.3 Conduct interviews
        1.1.4 Summarize findings
    1.2 Requirements Capture
        1.2.1 Gather inputs
        1.2.2 Draft requirements
        1.2.3 Review and update

2.0 Solution Design
    2.1 Architecture Modeling
        2.1.1 Create high-level diagrams
        2.1.2 Validate assumptions
        2.1.3 Finalize model
    2.2 Interface Design
        2.2.1 Draft prototypes
        2.2.2 Conduct walkthroughs
        2.2.3 Update for approval

3.0 Implementation
    3.1 Module A Build
        3.1.1 Configure core functions
        3.1.2 Internal testing
    3.2 Module B Build
        3.2.1 Configure functions
        3.2.2 Testing

4.0 Testing & Validation
    4.1 Test Plan Creation
    4.2 UAT Execution

5.0 Deployment
    5.1 Training
    5.2 Go-Live prep