Skip to content
Tutorials Center
My learning

Topics

Lesson 12 of 41 ยท Scope, Time and Cost

Project Scope Management

Learn how to define project scope: requirements gathering, the scope statement, product versus project scope, exclusions, validation, scope creep and a change control routine.

Scope is the sum of all the work required to deliver the product, service or result, and only that work. Scope management is about making that boundary clear, agreeing it with stakeholders and defending it sensibly as the project proceeds. It is the first leg of the triple constraint: if scope is vague, time and cost cannot be reliable either.

Product scope and project scope

  • Product scope: the features and functions of the result ("an online store with search, cart and card payment").
  • Project scope: the work needed to produce it ("research, design, build, test, train, migrate data, manage the project").

Both must be defined. A team that agrees on features but forgets data migration and training will overrun.

The scope management process

  1. Plan scope management: decide how scope will be defined, validated and controlled.
  2. Collect requirements: find out what stakeholders need.
  3. Define scope: write a detailed scope statement.
  4. Create the WBS: decompose the scope into manageable pieces (see Work Breakdown Structure).
  5. Validate scope: get formal acceptance of deliverables.
  6. Control scope: monitor status and manage changes to the baseline.

Collecting requirements

Techniques include interviews, workshops, surveys, observation, prototypes, document analysis and user stories. Capture three kinds of requirement:

  • Business requirements: why the project exists ("reduce support calls by 20%").
  • Stakeholder and functional requirements: what the product must do.
  • Non-functional requirements: how well it must do it (performance, security, accessibility).

A requirements traceability matrix links each requirement to its source, its deliverable and its test, so nothing is built without a reason and nothing required is forgotten.

Prioritize with a method such as MoSCoW: Must have, Should have, Could have, Won't have (this time). It turns "everything is urgent" into a conversation about what to cut if time runs out.

Python MoSCoW prioritization

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.

The scope statement

The project scope statement describes the project deliverables, acceptance criteria, exclusions, constraints and assumptions. The most useful part is the exclusions list: writing "not included: mobile app, data from before 2020" prevents later arguments.

Section Example
Deliverables Web store, admin panel, user guide
Acceptance criteria Passes all Must test cases; page load under 3 s
Exclusions Mobile app; integration with the old ERP
Constraints Go-live by 1 Nov; budget cap
Assumptions Product data supplied in CSV by customer

Scope creep

Scope creep is uncontrolled growth in scope without matching changes in time, cost or resources. It rarely arrives as one big request; it arrives as many small ones: "could you just add...". Sources include vague requirements, weak change control, gold plating (developers adding unrequested extras), stakeholders discovering needs late, and the manager saying yes to be liked.

Defences:

  • Clear, signed scope with exclusions.
  • A change control process that makes cost and time visible.
  • Frequent reviews with customers so surprises come early.
  • Saying "yes, and here is the effect on time and cost".

Change is not the enemy. Good change requests, evaluated and approved, are healthy. In adaptive projects the backlog is expected to change, but the scope of each iteration is still protected.

Validating and controlling scope

Validate scope is formal acceptance by the customer of completed deliverables against the acceptance criteria. It is different from quality control, which checks the deliverable is correct before it is shown to the customer. Control scope compares work performed to the baseline and handles variances and change requests.

Python Measure scope creep

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.

Scope in practice for software

For software, write the scope as user-visible capabilities and put a limit on integrations and data volumes. Use the definition of done to say when a feature is complete: coded, reviewed, tested, documented, deployed. A feature that is "90% done" is not done.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is scope creep?

    Small additions accumulate and hurt time, cost and quality.
  2. 2. In MoSCoW, what does 'Won't' mean?

    Won't have means agreed to be left out this time; it can return later.
  3. 3. Which part of a scope statement prevents later arguments most?

    Stating what is not included makes expectations explicit.
  4. 4. Validate scope means...

    Validation is formal acceptance against the acceptance criteria.

Summary

  • Scope is all the work, and only the work, needed to deliver the result.
  • Collect requirements, prioritize them (MoSCoW) and write a scope statement with exclusions.
  • Guard against scope creep with change control, not refusal.
  • Validate scope by customer acceptance and control it by comparing with the baseline.

Next: Work Breakdown Structure