Requirement Change Impact Analysis

A stakeholder wants to change a requirement mid-sprint. Analyze the impact.

ORIGINAL REQUIREMENT:
[What was agreed]

REQUESTED CHANGE:
[What the stakeholder now wants]

CURRENT STATUS:
- Development progress: [Not started / In progress / Complete]
- Testing progress: [Not started / In progress / Complete]
- Dependencies built on original requirement: [List any]

Analyze:
1. What code/work would need to change
2. What stories are affected (directly and indirectly)
3. Effort to implement the change vs. effort already invested
4. Risk of introducing bugs in completed work
5. Sprint impact (can this sprint still meet its goal?)

Present options:
- Option A: Make the change now (impact: ...)
- Option B: Ship as-is, change in next sprint (impact: ...)
- Option C: Compromise approach (describe)