How to Control Scope Creep by Embracing Change
summary
Explains a concrete change control system: use a 20–30% change budget separate from project cost, require written change requests and a change log, and make the client the approver so frivolous edits die. Uses a two‑step proposal with a content‑first deep dive, the 80‑hour deliverable rule, and strict no‑work‑until‑signed policy. Provides a downloadable sample change control plan and templates to apply the process immediately.
AI-written summary · about
chapters (11)
- 0:00Introduction to scope creep
- 3:12What you will learn today
- 4:16Defining scope creep clearly
- 9:20Proof this method works
- 11:47Educate clients on change
- 13:11Abandon the crystal ball
- 16:38Change budget explained
- 21:01Elements of change control
- 24:58Example of good process
- 28:32Review and key takeaways
- 29:16Resources and closing
