The scope creep antidote
One core workflow, written success metrics, and a 'not in v1' list — our sprint scoping ritual.
Scope creep kills sprint margins and client trust. Our antidote is a ritual, not willpower.
The "not in v1" list
Every sprint starts with a written list of things we are not building. Clients sign off on it.
Success metrics upfront
"If we ship X, how do we know it worked?" — one metric, measurable in week one.
Change requests = new scope
Mid-sprint additions get logged. We either swap something out or quote a follow-up — never silently absorb.
The weekly checkpoint
Even in a 7-day sprint, day 4 is a "are we still on scope?" async check. Catching drift early saves the deadline.
Related articles
Async client communication that actually works
Daily updates, Loom walkthroughs, and decision logs — how we run projects without daily standups.
Read articlePricing your MVP before you build
Fixed-price scoping: how we estimate MVPs without scope creep eating the margin.
Read article