Module 26 · Specialist · 8 min read

Scope creep and change requests

You will be able to: Recognise scope creep and where it comes from; Run a change control process; Price and decide changes using contingency.

  • Read not done yet
  • Self-check: not taken not done yet
  • Lesson complete not done yet

Scope creep is the slow addition of work with no change to time or money. Nobody decides it; it happens in small yeses. The cure is a simple change process that is applied to everything, including small things and including requests from the sponsor.

Where it comes from

  • Requirements that were never written down precisely.
  • Clients seeing the system and thinking of new things (this is natural).
  • Key users asking for 'just one more column'.
  • Consultants who like to say yes.

The change control process

  1. Capture the request in writing: who, what, why, urgency.
  2. Classify it: clarification of existing scope, defect, or change.
  3. Assess impact: effort, cost, schedule, risk, and effect on other parts of the design.
  4. Decide: the project sponsor approves, rejects or postpones.
  5. Record in the change log and update the blueprint, scripts and training if needed.
  6. Do the work only after written approval.
FieldExample
CR numberCR-02
RequestAdd a second approval step for invoices above AED 200,000
Requested byOwner
ClassChange
Impact0.25 day configuration, 0.25 day retest
CostAED 600 at AED 1,200 a day
DecisionApproved, using contingency
Four changes against contingencyThe estimate had 4.2 days of contingency. CR-01 extra approval step 0.25 day (AED 300); CR-02 new management report 1.5 days (AED 1,800); CR-03 extra price list import 0.5 day (AED 600); CR-04 extra print layout 1.75 days (AED 2,100). Total: 0.25 + 1.5 + 0.5 + 1.75 = 4.0 days, or 4.0 x 1,200 = AED 4,800. The contingency left is 4.2 - 4.0 = 0.2 day, and the sponsor sees the burn before the next request.

How to say it

Say yes with a price, not no with a lecture: 'We can do that. It is about a day and a half and would move go-live by two days. Shall I log it?' If the request needs a feature Zeyto does not have, record it as a custom request: you will pass it to Zeyto, you cannot promise a date, and here is a workaround for go-live.

Watch outA change that looks tiny, such as moving a field, may touch print templates, scripts and training. Always assess the knock-on effects before saying 'ten minutes'.
TipReview the change log at every steering meeting. A visible log makes the cost of 'one more thing' visible to the person asking.

Practise in the demo

  1. Write a change request for a new report, with effort, cost and decision fields.
  2. Calculate the contingency left if three changes of 0.5, 1 and 1.25 days are approved against 4.2 days.
  3. Open https://demo.zeyto.app/demo-app/ and sign in with the demo login. This is a public demo with sample data, so nothing you do there affects a real business.
Open the live demo

Public demo company, sign in as admin / demoAdmin123. Data refreshes nightly.

Key takeaways
  • Scope creep is unpriced additions; the cure is written change control for everything.
  • Assess impact on effort, cost, schedule and other deliverables before approval.
  • Say yes with a price, and treat product gaps as requests with no promised date.

Check yourself

5 questions on this lesson. Not timed, not the exam, and you can try again. Score 60% or more, and read the lesson, to complete it.

1. What is scope creep?

2. What must a change request include?

3. Four changes are approved: 0.25, 1.5, 0.5 and 1.75 days against 4.2 days of contingency. How much contingency is left?

4. The total of the four changes above is 4.0 days at AED 1,200 a day. What is the cost?

5. The owner insists a feature Zeyto lacks be delivered by go-live in two weeks and wants your promise. What do you do?

Practice questions for this module · Printable study sheet