Governance · tool 7 of 14
Change Control
Change Control: lets a project change on purpose instead of by accident.
Best for: Any project with an approved baseline · Time: 15 min per change
Domain: Governance · Focus area: Monitoring and Controlling
How it works
Change is normal; unmanaged change is the problem. Each request is written down, its impact on scope, time, cost, quality and risk is assessed, and someone with the authority decides. In adaptive work the same job is done by reprioritizing the backlog.
- No request is too small to log, though small ones can be fast.
- Assess impact before anyone starts work.
- Decide who can approve what, and at which size.
How to apply it
- Capture the request and who asked.
- Assess impact with the people doing the work.
- Approve, reject or defer, and record why.
- Update the plan and tell everyone affected.
The client asks for one more language. Impact: 6 days, €4k, launch moves a week. The sponsor approves it and drops a lower-value feature.
Say “yes, and here’s what it costs” rather than “no”. It keeps the relationship and the plan intact.
Use it
- Template: Change Log (blank), filled example
- Playbook: Scope keeps growing
Quick check
How is change usually managed in an adaptive project?
Sources
- PMBOK® Guide, 8th edition, and The Standard for Project Management (PMI, 2025)
Last reviewed 2026-11-02 against the PMBOK® Guide, 8th edition · Practitioner review pending · How this guide is made