Scoping & Cutting

Scope

Covers

• Converting a fuzzy initiative into a ship-able slice that fits a fixed time budget (“appetite”)
• Creating a cut list (what to drop/defer) with explicit trade-offs and rationale
• Defining an MVP as a hypothesis test (what you’re validating, not just “smaller”)
• Choosing a Minimum Lovable Slice (viable and emotionally resonant) instead of a “barely works” release
• Using Wizard-of-Oz / concierge approaches to validate value before building full automation
• Preventing scope creep via explicit non-goals + change control

When to use

• “Cut scope / descope this feature so we can ship by .”
• “Define an MVP for this initiative (what hypothesis are we testing?).”
• “We have 2–6 weeks; what can we ship that still matters?”
• “Scope creep is killing us; define what’s in/out and how changes happen.”
• “We need a minimum lovable version, not a compromised mess.”