SkarpSkarp

Chapter 7 of 21

Scope Foundations: From Requirements to the Work Breakdown Structure

See how vague ideas from stakeholders are transformed into a clear, structured picture of all the work the team must deliver—without leaving dangerous gaps or overlaps.

27 min readen

Big Picture: From Vague Ideas to a Scope Baseline

Why Scope Foundations Matter

Your job in a predictive project is to turn fuzzy stakeholder wishes into a precise, approved map of the work. That map is built from requirements, scope, and the scope baseline.

Key Definitions

A project is "A temporary endeavor undertaken to create a unique product, service, or result." A stakeholder can affect or be affected by project decisions, activities, or outcomes.

Predictive Life Cycle Context

In a predictive life cycle, scope, time, and cost are determined early. Stable, documented scope is essential because schedule and cost baselines depend on it.

Transformation Path

The path is: requirements → scope → scope baseline → WBS and work packages. CAPM questions often hide scope issues inside schedule, cost, or quality scenarios.

Requirements vs Scope in Predictive Projects

What Are Requirements?

Requirements express needs, expectations, and constraints. They answer: What does the customer or business need? They are the raw material for scope.

What Is Scope?

Scope describes what the project will deliver and the work needed to create it. It answers: What is included and excluded in this project to meet the requirements?

Requirements Traceability Matrix

A requirements traceability matrix is "A grid that links product requirements from their origin to the deliverables that satisfy them." It supports later WBS and change control.

Predictive vs Adaptive

Predictive: scope, time, cost set early. Adaptive: detailed scope is defined and approved before each iteration, often from a product backlog managed by the product owner.

The Scope Baseline: Components and Use

What Is the Scope Baseline?

The scope baseline is the approved reference for what the project will deliver. It sits in the project management plan and is used to control scope and manage changes.

Three Components

The scope baseline includes: 1) the project scope statement, 2) the work breakdown structure (WBS), and 3) the WBS dictionary. All three work together.

Project Scope Statement Role

The scope statement describes product scope, major deliverables, acceptance criteria, exclusions, and key constraints or assumptions related to scope.

Using the Baseline to Control Scope

You compare proposed work against the scope baseline to detect scope creep, support Validate Scope, and manage approved changes, just like you control cost vs the cost baseline.

Canonical Definitions: WBS and Work Package

Canonical WBS Definition

A work breakdown structure is "A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables."

Why the WBS Matters

It must cover 100% of the project work, avoid extras, and be organized around deliverables, not people or time. It is the backbone of scope planning.

Canonical Work Package Definition

A work package is "The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed."

Work Packages vs Activities

The WBS stops at work packages. The schedule then breaks work packages into activities. CAPM questions often test this distinction.

Building a Deliverable-Oriented WBS: Website Project

Start with the Main Deliverable

Example project: Corporate Marketing Website Redesign. Level 1 of the WBS is the full project deliverable representing the total project scope.

Major Deliverables (Level 2)

Think in deliverables: Project Management, User Research and Requirements, Visual and UX Design, Website Development, Testing and QA, Deployment and Training.

Decompose a Branch

For Website Development: Front-End Implementation, Back-End Integration, Content Migration, Security and Performance. Then break Front-End into templates and components.

Stop at Work Packages

You decompose until you can estimate cost and duration and assign ownership. Those lowest-level elements are work packages, the bottom of the WBS.

From WBS Deliverables to Activity Lists and Schedules

WBS vs Activities

The WBS holds deliverable-focused work packages. Schedule planning breaks each work package into activities, which are discrete tasks used for scheduling.

Example Linkage

Work package "Home Page Template" becomes activities like: create wireframe, review, design mockup, code HTML/CSS, peer review. These activities roll up to the work package.

Why This Link Matters

Activity durations and costs aggregate to work packages, feeding the cost and schedule baselines. You track progress at activity level, control at work package level.

Traceability Chain

Requirements → WBS deliverables → Work packages → Activities. This chain lets you show how each requirement is built and tested, and supports exam questions on traceability.

WBS Dictionary and Acceptance/Completion Criteria

Purpose of the WBS Dictionary

The WBS dictionary explains each WBS element in detail, especially work packages, so there is no ambiguity about what is included and when it is done.

Typical Contents

Entries usually include: WBS code, name, description, boundaries, owner, assumptions, related deliverables, completion criteria, acceptance criteria, and related requirement IDs.

Acceptance Criteria

Acceptance criteria are "A set of conditions that is required to be met before deliverables are accepted." They reflect the customer or sponsor’s view of "good enough".

Using the Dictionary to Avoid Disputes

When there is confusion about what a work package covers or when it is done, the WBS dictionary is your reference. CAPM questions often use it as the correct tool to clarify scope.

Thought Exercise: Decompose a Simple Project

Try this short exercise to practice deliverable-oriented decomposition and work package thinking.

Scenario

You are managing a small predictive project: Organize a One-Day University Tech Workshop for 80 students.

  1. List 4–6 major deliverables (Level 2 of the WBS)

Think in terms of "things" you will deliver, not tasks or people. For example, instead of "Call speakers", think of what that call is trying to produce.

Write your own list before checking the sample below.

  1. Propose 2–3 work packages under one deliverable

Choose one of your Level 2 deliverables and break it down until each element could reasonably have its cost and duration estimated and managed.

  1. Draft completion and acceptance criteria for one work package

Pick one work package and write:

  • Completion criteria (team perspective): How will the team know the work is complete?
  • Acceptance criteria (customer/sponsor perspective): What conditions must be met before they accept it?

Sample answer (compare after you try)

Possible Level 2 WBS elements:

  • 1.0 Project Management
  • 2.0 Venue and Logistics
  • 3.0 Speakers and Agenda
  • 4.0 Marketing and Registration
  • 5.0 On-site Execution
  • 6.0 Post-Event Wrap-Up

Under 3.0 Speakers and Agenda, example work packages:

  • 3.1.1 Keynote Speaker Confirmed
  • 3.1.2 Panel Session Confirmed
  • 3.1.3 Final Agenda Document

For 3.1.3 Final Agenda Document:

  • Completion criteria: "Agenda drafted, internally reviewed, and formatted; includes all sessions, times, speakers, and room assignments."
  • Acceptance criteria: "Approved by faculty sponsor; published on website; emailed to registered attendees 5 days before event."

Reflect: Did you stay deliverable-focused? Did your work packages feel small enough to estimate cost and duration?

Quiz 1: Scope Baseline and WBS Basics

Test your understanding of the scope baseline and WBS fundamentals.

Which of the following is the BEST description of the scope baseline in a predictive project?

  1. A list of all project requirements and the product backlog, used to prioritize work each iteration.
  2. The approved version of the project scope statement, WBS, and WBS dictionary, used as a basis for comparison during Validate Scope and Control Scope.
  3. A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
  4. A detailed list of schedule activities and milestones, used as the reference for tracking schedule variance.
Show Answer

Answer: B) The approved version of the project scope statement, WBS, and WBS dictionary, used as a basis for comparison during Validate Scope and Control Scope.

Option 2 is correct: the scope baseline consists of the approved project scope statement, WBS, and WBS dictionary, and it is used to control scope and support Validate Scope. Option 1 incorrectly mixes predictive and adaptive concepts and mentions a product backlog, which is not part of the scope baseline. Option 3 is the canonical definition of the WBS, which is only one component of the scope baseline. Option 4 describes the schedule baseline, not the scope baseline.

Quiz 2: Work Packages and Activities

Check your ability to distinguish work packages from activities and link WBS to scheduling.

You are preparing the schedule for a predictive construction project. The WBS includes a lowest-level element called "2.3.1 Foundation Poured" with cost and duration estimates. What is the NEXT appropriate step before creating the network diagram?

  1. Break "2.3.1 Foundation Poured" into schedule activities such as formwork, rebar placement, concrete pour, and curing.
  2. Reorganize the WBS to group work by trades (e.g., electricians, plumbers, masons) instead of deliverables.
  3. Compress the schedule by fast tracking the foundation work with framing to save time.
  4. Update the product backlog to reflect the new work package and re-prioritize items.
Show Answer

Answer: A) Break "2.3.1 Foundation Poured" into schedule activities such as formwork, rebar placement, concrete pour, and curing.

Option 1 is correct: the next step is to define schedule activities by decomposing the work package into smaller tasks that can be sequenced in a network diagram. Option 2 undermines the deliverable-oriented nature of the WBS. Option 3 refers to schedule compression (fast tracking) but you first need defined activities and a network. Option 4 incorrectly introduces a product backlog, which is an adaptive artifact and not used in this predictive construction scenario.

Key Term Review: Scope Foundations

Use these flashcards to reinforce the canonical definitions and core concepts from this module.

Project (canonical definition)
A temporary endeavor undertaken to create a unique product, service, or result.
Stakeholder (canonical definition)
An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
Predictive life cycle (canonical definition)
A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
Adaptive life cycle (canonical definition)
A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
Work breakdown structure (WBS) (canonical definition)
A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
Work package (canonical definition)
The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed.
Requirements traceability matrix (canonical definition)
A grid that links product requirements from their origin to the deliverables that satisfy them.
Product backlog (canonical definition)
An ordered list of everything that is known to be needed in the product, managed by the product owner.
Acceptance criteria (canonical definition)
A set of conditions that is required to be met before deliverables are accepted.
Scope baseline components
1) Project scope statement, 2) Work breakdown structure (WBS), 3) WBS dictionary.
Purpose of the WBS dictionary
To provide detailed information about each WBS element, especially work packages, including descriptions, boundaries, ownership, assumptions, and completion/acceptance criteria.

Key Terms

project
A temporary endeavor undertaken to create a unique product, service, or result.
stakeholder
An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
work package
The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed.
activity list
A documented tabulation of schedule activities that shows the activity description, identifier, and a sufficient scope of work description so project team members understand what work is to be performed.
WBS dictionary
A supporting document that provides detailed information about each element in the WBS, especially work packages, including descriptions, boundaries, ownership, assumptions, and completion and acceptance criteria.
scope baseline
The approved version of the project scope statement, WBS, and WBS dictionary, used as a basis for comparison during Validate Scope and Control Scope.
product backlog
An ordered list of everything that is known to be needed in the product, managed by the product owner.
acceptance criteria
A set of conditions that is required to be met before deliverables are accepted.
adaptive life cycle
A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
predictive life cycle
A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
work breakdown structure
A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
requirements traceability matrix
A grid that links product requirements from their origin to the deliverables that satisfy them.

Finished reading?

Test your understanding with a custom practice exam on this chapter.

Test yourself