scope-management

name	Scope Management
description	Detect scope creep, define MVPs, manage project boundaries, and prioritize work to keep initiatives focused and on track.

Purpose

Keep projects focused on what matters. Scope creep is the silent killer of projects: requirements grow incrementally until the original goal is unachievable within the original timeline and budget. This skill provides frameworks for defining, defending, and adjusting scope.

Steps

1. Define the project scope clearly:
   • In scope: What will be delivered (specific deliverables)
   • Out of scope: What will NOT be delivered (explicit exclusions)
   • Assumptions: What conditions are assumed true
   • Constraints: Budget, timeline, resource, and technology limits
2. Identify the MVP (Minimum Viable Product): what is the smallest version that delivers value?
3. Prioritize requirements using MoSCoW:
   • Must have: Project fails without these
   • Should have: Important but not critical for launch
   • Could have: Nice to have if time allows
   • Won't have: Explicitly deferred (this time)
4. Create a scope document in Word with clear boundaries
5. When new requests arrive, evaluate against scope:
   • Does it align with the project's original objective?
   • What is the impact on timeline, budget, and resources?
   • What must be removed to accommodate it (trade-off)?
6. Document scope change requests formally:
   • Description of the change
   • Business justification
   • Impact assessment (time, cost, quality, risk)
   • Approval: accepted, deferred, or rejected
7. Send scope change decisions to stakeholders via Outlook

Scope Creep Detection

Signal	What it means
"While you're at it, can you also..."	New requirement disguised as minor addition
"This should be easy to add"	Scope expansion without impact assessment
Requirements growing between meetings	Undocumented additions
"We assumed this was included"	Gap between expectations and documented scope
Timeline slipping with no scope reduction	Creep has already happened

Scope Change Evaluation Template

Question	Answer
What is being requested?	[Clear description]
Why is it needed?	[Business justification]
What is the timeline impact?	[Days/weeks added]
What is the cost impact?	[Additional budget needed]
What must be removed to fit it in?	[Trade-off or "nothing: timeline extends"]
Decision	Accepted / Deferred / Rejected
Approved by	[Name and date]

Prioritization Techniques

Effort vs. Impact Matrix

	Low Effort	High Effort
High Impact	Do first (quick wins)	Plan carefully
Low Impact	Do if time allows	Don't do

Time-Boxing

When scope cannot be reduced, fix the timeline and let scope flex within it:

1. Set a hard deadline
2. Prioritize features by business value
3. Build in priority order until time runs out
4. Whatever is not done is deferred, not "failed"

Output Format

• Word document: scope statement with in/out scope, MoSCoW priorities, and MVP definition
• Excel workbook: scope change log with status tracking
• Outlook email: scope change decisions to stakeholders

Guidelines

• "Out of scope" is a feature, not a failure. Say it early and clearly.
• Every scope addition must answer: "What are we NOT doing instead?"
• Document scope verbally agreed in meetings as written confirmation via email
• Review scope at every status report; catch creep early
• Protect the MVP: if Must-haves are at risk, everything else is deferred
• Never add scope without updating the timeline and budget estimate