SkarpChapter 6 of 20
Scope Foundations and the Work Breakdown Structure
Turn broad ideas into a clear, manageable picture of the work by structuring scope with a work breakdown structure and defining work packages you can estimate and control.
Scope Foundations: Product vs Project Scope
Why Scope Matters
In predictive projects, scope is the backbone of planning. Before you build a WBS, you must know exactly what is in scope and what is not.
Product vs Project Scope
Product scope describes the features, functions, and characteristics of the product, service, or result. Project scope describes the work needed to deliver that product.
Banking App Example
For a mobile banking app, product scope covers things like biometric login and transfers. Project scope covers workshops, design, coding, testing, training, and deployment.
Predictive Life Cycle Context
In a predictive life cycle, you try to stabilize both product and project scope early. Changes are possible but must go through formal change control.
Exam Tip
In questions, ask: am I talking about the characteristics of the thing (product scope) or the work to create it (project scope)? This distinction appears often.
The Predictive Life Cycle and Scope Baseline
Predictive Life Cycle
A predictive life cycle is "a development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle."
What Is the Scope Baseline?
The scope baseline is the approved version of scope components: the scope statement, WBS, and WBS dictionary. It is part of the project management plan.
Scope Statement, WBS, WBS Dictionary
1) Scope statement describes project and product scope. 2) WBS shows all work in a hierarchy. 3) WBS dictionary details each WBS element, especially work packages.
Using the Scope Baseline
You compare actual or requested work to the scope baseline. It guides change analysis and helps resolve disputes about what is included in the project.
Canonical Definitions: WBS and Work Package
WBS: Canonical 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."
Understanding the WBS
Hierarchical means levels; decomposition means breaking work down; total scope means nothing missing or extra. The WBS is deliverable-oriented, not a task list.
Work Package: Canonical 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 Package in Practice
You stop decomposing when a piece of work is small enough to estimate, assign, and control. Activities are then derived from each work package.
Building a Simple WBS: Campus Event Project
Step 1: Top-Level Deliverable
For a one-day university tech fair, Level 1 of the WBS might be: "University Tech Fair 2026 Delivered".
Step 2: Major Deliverables
Level 2 could include: 1.1 Event Concept, 1.2 Venue and Logistics, 1.3 Exhibitors, 1.4 Marketing, 1.5 Operations, 1.6 Project Management.
Step 3: Decompose a Branch
Take 1.2 Venue and Logistics and break it into deliverables like 1.2.1 Venue Contract Signed and 1.2.3 Catering Arrangements Confirmed.
Reach Work Packages
Decompose 1.2.3 into work packages: 1.2.3.1 Catering Requirements Finalized, 1.2.3.2 Vendor Selected, 1.2.3.3 Schedule Finalized.
From WBS to Activities
At the work package level, you estimate cost and duration, assign owners, and later derive detailed schedule activities from each work package.
From WBS Deliverables to Activities and Schedule
Scope to Schedule Flow
Requirements lead to the scope statement and WBS. From work packages you derive activities, then sequence them into a schedule network and baseline.
Roles of WBS vs Activities
WBS deliverables and work packages define what must be done. The activity list and network diagram define how and when it will be done.
Catering Work Package Example
Work package "Catering Vendor Selected and Contracted" may generate activities like identify vendors, issue RFP, evaluate, negotiate, and sign.
Exam Trap
Do not put detailed step-by-step tasks in the WBS. Those belong in the activity list and schedule, not as separate WBS elements.
Scope Creep and Using the Scope Baseline to Control Changes
What Is Scope Creep?
Scope creep is uncontrolled expansion of product or project scope without corresponding changes to time, cost, or resources.
Scope Baseline as Defense
The scope statement, WBS, and WBS dictionary together form the scope baseline, your main tool for resisting uncontrolled changes.
Change Control Steps
Compare the request to the baseline, document it, analyze impacts, seek approval via integrated change control, then update baselines if approved.
Portal vs Mobile App Example
If a sponsor adds a mobile app to a web-only project, this is scope increase. You must use formal change control, not just "fit it in".
WBS Dictionary and Acceptance Criteria: Making Work Packages Clear
Purpose of the WBS Dictionary
The WBS dictionary adds detail to WBS elements: descriptions, boundaries, assumptions, owners, and especially acceptance criteria.
Acceptance Criteria Definition
Acceptance criteria are "a set of conditions that is required to be met before deliverables are accepted."
Sample Entry
For work package 1.2.3.2 Catering Vendor Selected and Contracted, the dictionary would detail scope, boundaries, owner, and acceptance conditions.
Exam Use
If there is confusion about what a work package includes, the project manager should review or update the WBS dictionary, not guess or improvise.
Thought Exercise: Decompose Your Own Mini-Project
Apply what you have learned by decomposing a simple, familiar project into a WBS with work packages.
Scenario: You are planning a student hackathon weekend at your university. The project uses a predictive approach: you must commit to scope, schedule, and budget three months before the event.
Your task (no grading here, just practice):
- Define the Level 1 deliverable
- Write a short phrase that describes the fully delivered project (e.g., "Spring 2027 Student Hackathon Delivered").
- Identify 4–6 Level 2 deliverables
- Think deliverables, not activities. For example:
- Hackathon Concept and Rules Defined
- Venue and Infrastructure Ready
- Sponsors and Prizes Secured
- Participant Registration Completed
- Event Operations Executed
- Project Management Performed
- Pick one branch and decompose to work packages
- Choose "Sponsors and Prizes Secured" (or another branch) and break it into smaller deliverables.
- Keep decomposing until each item is small enough that you could reasonably:
- Estimate its cost and duration
- Assign it to one owner
- Track its completion clearly
- Mark those lowest-level items as work packages.
- Add acceptance criteria for one work package
- For example, for "Gold Sponsor Contract Signed":
- Contract value at least $5,000
- Sponsor logo and usage rights agreed
- Payment schedule defined
As you do this, check yourself:
- Are you staying deliverable-oriented?
- Can each work package be estimated and managed?
- Could you defend the scope using your WBS if someone asked for "just one more" feature?
Quick Check: WBS and Work Package Basics
Test your understanding of core definitions and concepts.
Which statement best describes a work package in a predictive project?
- A group of related activities that appears at any level of the WBS and is used mainly for reporting.
- The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed.
- A single task in the activity list that must be completed by one person within one day.
- Any WBS element that represents a major deliverable or phase of the project.
Show Answer
Answer: B) The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed.
The canonical definition of 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." It is not just any WBS element or a single one-day task.
Scenario Quiz: Scope Creep and Baselines
Apply your knowledge to a realistic scenario.
You are managing a predictive project to build a university portal. The approved scope baseline includes only web functionality. Midway through, a senior stakeholder informally asks your team to "add a simple mobile app" without changing the deadline or budget. What is the BEST action?
- Agree to build the app if the team believes it can be done within the existing schedule.
- Update the WBS to include the mobile app and inform the sponsor after it is complete.
- Explain that the request is outside the approved scope baseline and initiate integrated change control to assess and approve or reject the change.
- Reject the request immediately and tell the stakeholder that scope is frozen and cannot be changed.
Show Answer
Answer: C) Explain that the request is outside the approved scope baseline and initiate integrated change control to assess and approve or reject the change.
The mobile app is outside the approved scope baseline. The best response is to use the scope baseline as a reference and initiate integrated change control to analyze impacts and seek a formal decision. Quietly accepting or rejecting without process is not appropriate.
Key Scope and WBS Terms Review
Flip through these cards to reinforce critical definitions and relationships. Aim to recall the answer before revealing it.
- Predictive life cycle (definition)
- 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 (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 (definition)
- The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed.
- Product scope vs project scope
- Product scope: features and characteristics of the product, service, or result. Project scope: the work that needs to be done to deliver that product with those features.
- Scope baseline components
- Approved project scope statement, work breakdown structure (WBS), and WBS dictionary.
- Acceptance criteria (definition)
- A set of conditions that is required to be met before deliverables are accepted.
- Purpose of the WBS dictionary
- To provide detailed information about each WBS element, especially work packages, including descriptions, boundaries, assumptions, owners, and acceptance criteria.
- Scope creep (concept)
- Uncontrolled expansion of product or project scope without corresponding adjustments to time, cost, and resources, often bypassing formal change control.
- Link between WBS and schedule
- Work packages in the WBS define what must be done; detailed schedule activities are derived from these work packages and then sequenced and timed.
Key Terms
- scope creep
- Uncontrolled expansion to product or project scope without adjustments to time, cost, and resources.
- 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 sufficient detail to understand the work to be performed.
- product scope
- The features, functions, and characteristics of the product, service, or result that is being created.
- project scope
- The work that needs to be performed to deliver a product, service, or result with the specified features and functions.
- WBS dictionary
- A supporting document that provides detailed information about each element in the work breakdown structure, especially work packages, including descriptions, boundaries, assumptions, owners, and acceptance criteria.
- scope baseline
- The approved version of the scope statement, work breakdown structure (WBS), and WBS dictionary that can be changed only through formal change control procedures.
- acceptance criteria
- A set of conditions that is required to be met before deliverables are accepted.
- 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.
- integrated change control
- A process in which change requests are formally documented, evaluated for impact on scope, schedule, cost, and other constraints, and then approved, deferred, or rejected in a coordinated way.