Skip to content
Tutorials Center
My learning

Topics

Lesson 27 of 41 ยท Risk, Quality and Communication

Change Control

Manage project change safely: change requests, impact analysis, the change control board, baselines, scope creep and an example change log in Python.

Every project changes. Customers learn what they really want, regulations move, suppliers fail, technology surprises you. The danger is not change itself but uncontrolled change: a small favor here, a quick tweak there, until the plan nobody follows has nothing to do with the work being done. This is scope creep, and it is one of the top reasons projects run over budget.

Change control is the process that lets a project say "yes, if we understand the consequences" instead of either "no, never" or "sure, no problem".

Baselines: what you change against

A baseline is the approved version of the scope, schedule and cost that you measure performance against. Once approved, it can change only through a formal process. Without a baseline you cannot even say that something changed; there is nothing to compare with. A change that is approved produces a new baseline version (v1.0, v1.1) and the old one is kept for history.

The change control process

From request to baseline

Request Anyone logs a change request.
Assess Analyze impact on scope, time, cost, risk.
Decide Change control board approves or rejects.
Implement Update plans and do the work.

Then verify, close the request and tell everyone.

1 / 2
  1. Log the request. Capture the requester, description, reason, priority and date in a change log.
  2. Assess the impact. Which deliverables, tasks, costs, dates and risks are affected? What if we do not make the change? What are the alternatives?
  3. Decide. Small changes within the project manager's authority are decided by the manager. Big ones go to the change control board (CCB): a small group of sponsor, customer, technical and business representatives who can commit money and scope.
  4. Implement. Update the scope statement, WBS, schedule, budget, risk register and communications. Communicate the change.
  5. Verify and close. Check that the change did what was promised and archive the record.

An emergency change (a production outage fix) may be approved by a delegate first and documented immediately afterwards.

Never say a plain "no" to a request in the hallway. Say "log it and we will assess it". The request may be valuable, and the customer sees that the process works.

Impact analysis in practice

An impact analysis converts a vague "could you add X?" into numbers. For each request estimate extra effort, the cost, and the effect on the critical path (see the scheduling chapter). Include indirect effects: more testing, training, documentation, and a larger maintenance load.

Python Impact analysis for a change request

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.

Present options, not a single answer: "Add it now and slip 2.5 days; add it in release 2 at no delay; drop feature Y to keep the date." The board then decides with the trade-off in front of them.

A change log you can query

A change log is just a table. Small as it is, it lets you answer management questions: how many changes were approved, what did they add in cost, which sources keep asking?

Python Change log summary

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.

If one source supplies most requests, the fix may be upstream: clearer requirements, an earlier demo, or a product owner empowered to say no.

Scope creep and how to prevent it

Scope creep is the gradual growth of scope without matching changes in time, budget or resources. Warning signs: "just one more small thing", gold plating (the team adds extras nobody asked for), vague requirements, and a sponsor who talks directly to developers.

Prevention:

  • A written, signed scope statement with explicit exclusions.
  • A visible WBS (work breakdown structure) so everyone sees what is in.
  • A single entry point for requests, and a single person accountable for scope (the product owner in agile teams).
  • Frequent demos so requirement gaps appear early, as cheap feedback instead of late change requests.

Not all change is bad. In agile projects change is welcome because the backlog is re-ordered each sprint; the control comes from limiting change within a sprint and from the product owner's authority (see Scrum).

Change control beyond scope

Changes can also hit the quality bar (quality management), add new risks, and change who needs to be informed (communication). A good change process asks about all three every time.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is scope creep?

    Creep is uncontrolled change; the same addition approved through change control is just a change.
  2. 2. Who typically has authority to approve large changes affecting scope and budget?

    The CCB or sponsor has the authority to commit money, time and scope.
  3. 3. A baseline is best described as:

    Baselines are approved versions of scope, schedule and cost; changes create new versions.
  4. 4. Which step comes right after logging a change request?

    You must understand the effects on scope, schedule, cost and risk before anyone decides.

Summary

  • Change is normal; uncontrolled change (scope creep) destroys plans.
  • Baselines are the reference; approved changes produce new baseline versions.
  • Process: log, assess impact, decide (CCB), implement, verify and close.
  • Present options with costs and schedule impact so decisions are informed.
  • Agile projects welcome change but protect each sprint and rely on the product owner.

Next: Agile Mindset and Principles