Build a scope creep defense document

Scope Creep Is Trade-Off Avoidance

Scope creep is rarely caused by one bad request — it is caused by the team's unwillingness to trade off. Every addition seems reasonable in isolation, and no single addition is worth the fight. Basecamp's Shape Up addresses this with the appetite rule: the budget is the six weeks, and scope is what fits within the budget. Linear's method operationalizes the same idea — new scope displaces existing scope or goes to the next cycle. Without a trade-off rule, every project becomes a scope ratchet that only expands.

How the Build a scope creep defense document Prompt Works

The prompt establishes the original boundary in writing, audits additions so the creep is visible, and establishes the load-bearing rule: any addition must replace an existing item of equal or larger scope. The memo step makes the rule public so stakeholders cannot slip additions through quiet channels.

When to Use It

• A cycle is 50% in and new asks are arriving weekly.
• Stakeholders are routing scope requests around the PM.
• A previous project blew through its timeline 2x due to creep.
• A new PM is establishing delivery discipline.
• Engineering is frustrated because the scope keeps growing.

Common Pitfalls

• Saying yes to "small" additions. "Small" adds compound. Five small additions equal one medium re-scope.
• No written boundary. A verbal scope boundary is not a boundary. Write it down, share it, reference it.
• Timeline extensions as the first lever. Extending the timeline teaches stakeholders that scope expands on request. Trade off instead.

Sources

• Shape Up — Basecamp
• The Linear Method — Linear
• Getting Real — Basecamp
• Agile Estimation — Atlassian