KEVOS® Project Delivery Handbook
Project Scope Management
If you ask a hundred project managers what kills projects, you will hear the same answer repeated in different accents: scope creep.
In this handbook article
- Why Scope Management Is the Most Important Function of a Project Manager
- What Is Project Scope Management?
- How Scope Management Works: The Five Components
- 1. Project Initiation
- 2. Scope Planning
- 3. Scope Definition
- 4. Scope Verification
- 5. Scope Change Control
- The FANGs of Scope Creep: A Holistic Framework
- The Pitfalls: Where Scope Management Goes Wrong
- Key Takeaways
If you ask a hundred project managers what kills projects, you will hear the same answer repeated in different accents: scope creep. But scope creep is not a disease — it is a symptom. The real disease is inadequate scope management. This article dismantles the discipline from the ground up.
Why Scope Management Is the Most Important Function of a Project Manager
That is not an editorial opinion — it is a direct claim from the literature. Asadullah Khan, writing in Cost Engineering, states it plainly: managing the scope of a project is the most important function of a project manager, regardless of whether the project sits in industrial or non-industrial activity, manufacturing or service, private or public enterprise.
Why such a bold claim? Because scope is the master variable. Every other constraint — time, cost, quality — is downstream of scope. Change the scope and you change the budget. Change the scope and you change the schedule. Change the scope and you change the quality requirements. Effective scope management, therefore, is the prerequisite for effective management of everything else.
Kul Uppal reinforces this from the cost engineering perspective: data analysis from major engineering and construction projects reveals that the majority of rework and problems affecting project cycle time exist for two reasons:
1. Poor definition of project requirements (project scope of work) prior to preparing the cost estimate. 2. Failure to recognise invalid assumptions behind those project requirements.
These are not execution failures. They are scope failures.
What Is Project Scope Management?
Project scope management is the collection of processes that ensure a project includes all the work required — and only the work required — to complete the project successfully. It can be broken into five components, all of which revolve around a central artefact: the Work Breakdown Structure (WBS).
Relationship details
| From | Relationship | To |
|---|---|---|
| Project — Initiation | leads to | Scope — Planning |
| Scope — Planning | leads to | Scope — Definition |
| Scope — Definition | leads to | Scope — Verification |
| Scope — Verification | YES — Verified | Project — Completion |
| Scope — Verification | NO — Issues Found | Scope Change — Control |
| Scope Change — Control | leads to | Scope — Planning |
| WORK BREAKDOWN — STRUCTURE — (WBS) | leads to | Project — Initiation |
| WORK BREAKDOWN — STRUCTURE — (WBS) | leads to | Scope — Planning |
| WORK BREAKDOWN — STRUCTURE — (WBS) | leads to | Scope — Definition |
| WORK BREAKDOWN — STRUCTURE — (WBS) | leads to | Scope — Verification |
| WORK BREAKDOWN — STRUCTURE — (WBS) | leads to | Scope Change — Control |
The WBS is the spine of scope management. All five components interact with each other through the WBS. Everything included in the WBS is part of project scope. Anything not shown clearly in a WBS is out of project scope — including any implied activities.
How Scope Management Works: The Five Components
1. Project Initiation
Projects are initiated to satisfy a business need. That need may originate from several sources:
Relationship details
| From | Relationship | To |
|---|---|---|
| Market — Demand | leads to | PROJECT — INITIATION |
| Regulatory — Requirement | leads to | PROJECT — INITIATION |
| Customer — Requirement | leads to | PROJECT — INITIATION |
| Service — Improvement | leads to | PROJECT — INITIATION |
| Reliability — Improvement — (Revamp) | leads to | PROJECT — INITIATION |
| New Product / — Technology | leads to | PROJECT — INITIATION |
Once a business need is identified and aligned with strategic objectives, a feasibility analysis is conducted before the full-scale project is launched. This feasibility analysis has three dimensions:
| Feasibility Type | Key Questions |
|---|---|
| Technical | Is the technology available? Do we have competent management and operations teams? Is land, infrastructure, and feedstock available? |
| Economic | What are the benefit-cost ratios? What is the rate of return over the project's anticipated lifetime? |
| Financial | Are necessary funds available? What is the cost of borrowing? What is the owner organisation's credit rating? |
Key Output: A detailed feasibility analysis that allows management to give the go-ahead or shelve the project.
2. Scope Planning
Scope planning develops a summary and intermediate level WBS. At this stage, project scope is not detailed enough for a comprehensive breakdown — the team is working with progressive elaboration (also called rolling wave planning).
The scope planning phase produces:
- Summary and intermediate level WBS
- Design Basis Memorandum (DBM) — containing capacity, product characteristics, site data, and available infrastructure
- Invitation to Bid (ITB)
- Award of Basic Engineering Package (BEP) contract
WBS Organisational Choice: There is no single "correct" way to structure a WBS. Khan illustrates two valid approaches for the same petrochemical plant project:
| Approach | Structure | Best Suited For |
|---|---|---|
| Balanced Matrix (Project + Functional) | Top level by plant unit (Ethylene, Polyethylene, etc.); sub-levels by project phase (DBM, ITB, BEP, DED, Procurement, Construction, Commissioning) | Organisations with functional departments that contribute to multiple projects |
| Pure Project | Top level by project phase (DBM, ITB, BEP, DED, Procurement, Construction, Commissioning); sub-levels by plant unit | Dedicated project organisations with full authority over resources |
Relationship details
| From | Relationship | To |
|---|---|---|
| Petrochemical Plant Project | leads to | Process Units |
| Process Units | leads to | Reactors |
| Process Units | leads to | Distillation |
| Petrochemical Plant Project | leads to | Utilities |
| Utilities | leads to | Power & Steam |
| Utilities | leads to | Cooling Water |
| Petrochemical Plant Project | leads to | Offsites |
| Offsites | leads to | Tank Farm |
| Offsites | leads to | Loading Racks |
| Petrochemical Plant Project | leads to | Engineering |
| Engineering | leads to | Process Design |
| Engineering | leads to | Detailed Design |
| Petrochemical Plant Project | leads to | Procurement |
| Procurement | leads to | Equipment Supply |
| Procurement | leads to | Bulk Materials |
| Petrochemical Plant Project | leads to | Construction |
| Construction | leads to | Civil Works |
| Construction | leads to | Mechanical Erection |
| Petrochemical Plant Project | leads to | Commissioning |
| Commissioning | leads to | Pre‑Commissioning |
| Commissioning | leads to | Start‑Up |
3. Scope Definition
This is where the framework becomes detailed. The WBS is expanded to include details down to the work package level. The key activities include:
- Preparation of the Basic Engineering Package (BEP)
- Award of the Engineering, Procurement and Construction (EPC) contract
- Detailed Engineering Design (DED)
Critical rule: Everything in the WBS is in scope. Everything not in the WBS is out of scope. Many project managers have come to grief for not preparing a comprehensive enough WBS.
To mitigate cost risks from incomplete scope definition, two types of emergency funds are allocated:
| Fund Type | Purpose | Example |
|---|---|---|
| Management Reserve | Used for unexpected changes to project scope | A mandatory new regulatory requirement imposed mid-project |
| Contingency Fund | Used for expected additional work that cannot be accurately quantified | Amount of rework in engineering design; airfreight costs for expedited critical items |
The distinction matters. Management reserves address unknown unknowns. Contingency funds address known unknowns. Confusing the two — or failing to allocate either — is a common cause of budget blow-outs.
4. Scope Verification
Scope verification is the feedback loop. It involves checking all design and engineering deliverables against the requirements established during scope planning and definition.
Key characteristics:
- It is continuous, not sequential — it starts almost concurrently with scope planning and definition
- It is required for progress measurement and making progress payments to contractors
- It uses Earned Value Management (EVM) to compare actual verified work against scheduled work
Application of EVM in scope verification: Under-par performance on schedule and cost, once detected through earned value analysis, will soon produce schedule and cost overruns that are irreversible. Early detection through verification is the only defence.
Key Outputs: Procurement and construction proceed based on verified scope.
5. Scope Change Control
Scope change is an inevitable reality for any project. The goal is not to prevent all changes — it is to manage them so they do not become scope creep.
Scope creep is a term used to describe unauthorised scope changes. Unauthorised changes may creep into project scope through verbal instructions, email instructions, or written instructions issued without a full understanding of their magnitude.
Types, Reasons, and Nature of Changes
| Types of Change | Reasons for Change | Nature |
|---|---|---|
| Design specification change | Correct deficiency to meet safety, health, or environmental regulations | Discretionary (nice to have) |
| Process design development | Correct deficiency to meet operational requirements | Non-discretionary (essential) |
| Project execution change | Correct deficiency in cost estimate | |
| External budget transfer | Adjust budget to reflect changed execution basis | |
| Estimate adjustment | ||
| Field change | ||
| Commissioning change |
Key Outputs: Acceptance tests and commissioning.
The FANGs of Scope Creep: A Holistic Framework
Traditional scope management focuses almost exclusively on functional requirements. Hans Robbers, a senior programme manager specialising in distributed international projects, argues this is dangerously narrow. Budget overruns are not always caused by changes to functionality — they also arise from changes to project approach, governance, and non-functional requirements.
Robbers proposes the FANGs framework:
Relationship details
| From | Relationship | To |
|---|---|---|
| SCOPE CREEP | leads to | F — Functionality — Business & functional — requirements changes |
| SCOPE CREEP | leads to | A — Activities — Changes to project — approach & methodology |
| SCOPE CREEP | leads to | N — Non-Functional — Requirements — Performance, security, — scalability changes |
| SCOPE CREEP | leads to | G — Governance — Reporting, compliance, — audit requirements — added mid-project |
| FANG | What It Covers | Example of Creep | How to Control |
|---|---|---|---|
| Functionality | Business/functional requirements | Client requests an additional reporting module after sign-off | Standard change control procedure; separate budget for impact analysis |
| Activities | Project approach, methodology, environments | Team decides to add a UAT environment not in original plan | Baseline the project approach in the PEP; treat methodology changes as formal changes |
| Non-Functional | Performance, security, scalability, usability | Stakeholder demands 99.99% uptime instead of 99.9% | Document NFRs explicitly in scope definition; quantify impact of changes |
| Governance | Reporting, compliance, audit, steering structures | New regulatory body requires additional compliance reporting | Include governance overhead in initial estimates; flag regulatory risk early |
Practical Tip: Most projects have a change-control procedure for Functionality. Very few have formal change control for Activities, Non-Functional Requirements, or Governance. If you only guard one door, scope creep enters through the other three.
The Pitfalls: Where Scope Management Goes Wrong
1. The WBS is treated as an administrative artefact, not a management tool. If the WBS is built once and filed, it becomes useless. It must be a living document that evolves through progressive elaboration while remaining under change control.
2. Scope is defined too late. Uppal's research shows that poor definition of project requirements before preparing the cost estimate is the primary root cause of cycle time problems. Scope must be substantially frozen before full funding (the end of Phase 3 / FEL).
3. Scope planning is confused with scope definition. Planning produces a summary-level WBS. Definition produces a work-package-level WBS. Attempting to estimate costs or award contracts based on a summary-level WBS is a recipe for overruns.
4. Only functional scope is controlled. The FANGs framework reveals that activities, non-functional requirements, and governance are equally capable of causing budget blow-outs — yet they are rarely subject to formal change control.
5. The distinction between management reserves and contingency is blurred. When a single "contingency" line item is used to cover both expected and unexpected scope changes, the project team has no early warning system for distinguishing between planned flexibility and genuine scope creep.
Key Takeaways
- Scope management is the project manager's most important function because scope is the master variable — every other constraint depends on it.
- The WBS is the central artefact through which all five scope management components interact. If it is incomplete, everything downstream is unreliable.
- Two valid WBS structures exist (balanced matrix and pure project); the choice depends on how the owner organisation operates, not on a universal "best practice."
- Management reserves cover unknown unknowns; contingency funds cover known unknowns. Both must be explicitly allocated.
- Scope creep has four attack vectors, not one. The FANGs framework (Functionality, Activities, Non-functional requirements, Governance) provides a holistic defence.
- Scope must be frozen before full funding. The cost of scope changes rises exponentially as the project moves from planning into execution.
Next in the series: Part 3 — Monitoring & Controlling: Schedule, Cost & Earned Value Technique. We move from defining the plan to tracking it — with the quantitative tools that tell you, in real time, whether your project is on track or heading for disaster.