scoping

name	scoping
description	Define software project scope, MVP boundaries, non-goals, included work, excluded work, and acceptance boundaries. Use when preventing uncontrolled expansion or clarifying what will and will not be built.

Purpose

This skill helps turn goals and validated ideas into a bounded software project or feature scope.

Use this skill when:

• Defining an MVP
• Setting project boundaries
• Identifying non-goals
• Clarifying included and excluded work
• Containing scope creep
• Preparing work for prioritization or architecture

Inputs

Expected inputs:

• Goal or KPI
• Validated concept
• Target user
• User need
• Constraints
• Known non-goals
• Delivery timeframe

Goals usually come from goal-setting, while validated concepts usually come from validation. If success is not defined, use goal-setting before scoping.

Scoping Principles

Always optimize for:

1. Minimum useful capability
2. Explicit boundaries
3. Clear non-goals
4. Testable acceptance
5. Reduced ambiguity

Avoid optimizing solely for:

• Complete feature coverage
• Stakeholder wish lists
• Future-proofing
• Edge-case completeness
• Perfect first release

Process

Step 1: Define the Core Outcome

Clarify:

• Target user
• Problem being solved
• Success criteria
• Minimum behavior required
• Constraints that shape the solution

Flag goals that are too broad to scope.

---

Step 2: Separate Scope Categories

Classify work into:

Category	Meaning
Must Have	Required for the MVP to deliver value
Should Have	Important but not required for first release
Could Have	Useful follow-up work
Non-Goal	Explicitly excluded from this scope

Make non-goals as visible as included work.

---

Step 3: Identify Boundaries

Define:

• User flows included
• Data included
• Integrations included
• Admin or operational behavior
• Error handling expectations
• Deferred edge cases

---

Step 4: Produce Scope Statement

Generate:

• In-scope work
• Out-of-scope work
• MVP definition
• Acceptance boundaries
• Assumptions
• Open questions

Anti-Patterns

Avoid:

• Scoping before goals are clear
• Hiding non-goals
• Including every edge case in the MVP
• Mixing future roadmap items into current scope
• Using vague phrases like "improve experience" without boundaries
• Treating scope as fixed after new evidence appears

Reviewer Checklist

Before finalizing scope:

• Is there a clear MVP?
• Are non-goals explicit?
• Can the scope be tested against success criteria?
• Are deferred items named?
• Can prioritization and architecture use this scope?

Escalation Guidance

Escalate when:

• Required work exceeds capacity
• Stakeholders reject necessary non-goals
• Goals require mutually incompatible scope
• Legal, security, or compliance boundaries are unclear
• MVP cannot deliver meaningful value

Example

Input:

• Goal: Reduce onboarding tickets by 25%
• Idea: Guided onboarding checklist

Expected scope:

1. In scope: checklist for required setup steps
2. In scope: progress persistence and completion state
3. Out of scope: full onboarding redesign
4. Out of scope: custom workflows per enterprise customer

Recommended next skill:

• Use prioritization to order scoped work or architecture to design the implementation.