← All Simulationsagile-delivery v1.0.0

A Stakeholder Adds Scope Mid-Sprint

Context: During Sprint 4 of the core platform API overhaul, a senior executive from Sales contacts the engineering team directly, demanding an urgent custom reporting endpoint to close a major prospective enterprise deal by Friday afternoon.

The executive emails the Product Owner and lead developer, stating: 'If we don't have this custom reporting endpoint live by Friday 5 PM, the $500k Acme Corp deal is off the table. Please add it to the current sprint immediately.' What is your first action?

Linear Reader View (JavaScript Disabled)

Complete linear outline of all scenario decision paths, feedback, and post-mortem debriefs.

Node n1: The executive emails the Product Owner and lead developer, stating: 'If we don't have this custom reporting endpoint live by Friday 5 PM, the $500k Acme Corp deal is off the table. Please add it to the current sprint immediately.' What is your first action?

Option (c1_1): Absorb the request immediately into the active sprint backlog without removing any existing commitment. → Next: n2_overload

Feedback: Accepting additional scope without removing existing work compromises team capacity and risks failing all sprint commitments.

Option (c1_2): Acknowledge the urgency, schedule an immediate alignment call with the executive, Product Owner, and Tech Lead to evaluate impact and capacity. → Next: n3_tradeoff

Feedback: Collaborative trade-off evaluation maintains trust while protecting delivery quality and sprint integrity.

Option (c1_3): Refuse the request outright, citing strict sprint boundary rules prohibiting any mid-sprint changes. → Next: n4_conflict

Feedback: Rigid rejection without business context damages stakeholder trust and creates unnecessary organizational friction.

Node n2_overload: The team attempts to squeeze the custom endpoint into the current sprint alongside existing deliverables. By Wednesday, developers report severe context switching, broken integration tests, and escalating technical debt.

Option (c2_1): Pause and hold an emergency backlog re-alignment with the PO to swap out lower-priority stories of equal point value. → Next: n3_tradeoff

Feedback: Course-correcting by negotiating explicit trade-offs restores team focus and delivery feasibility.

Option (c2_2): Mandate weekend overtime for the engineering team to finish both original work and the custom endpoint. → Next: e_burnout

Feedback: Mandatory overtime causes burnout, high defect rates, and long-term delivery degradation.

Node n3_tradeoff: In the alignment meeting, the Product Owner demonstrates that adding the custom reporting endpoint requires 8 story points. The team evaluates their remaining capacity and proposes options to the executive.

Option (c3_1): Swap out 8 story points of non-critical sprint backlog items with explicit executive sign-off and PO agreement. → Next: e_success

Feedback: Explicit point-for-point exchange preserves total velocity while satisfying high-value business opportunities.

Option (c3_2): Fast-track a light MVP version of the endpoint for Friday, deferring full reporting filters to Sprint 5 top backlog position. → Next: e_defer_success

Feedback: Scope decomposition delivers immediate deal-closing value with minimal disruption to core sprint deliverables.

Node n4_conflict: The sales executive escalates to the VP of Product, complaining that the agile process is bureaucratic and blocking critical revenue growth.

Option (c4_1): Reframe the discussion around joint business outcomes, presenting clear trade-off options rather than process rules. → Next: n3_tradeoff

Feedback: Shifting from rule enforcement to shared business value de-escalates conflict and enables productive decisions.

Endings & Debriefs

Successful Sprint Trade-Off Negotiation

By conducting a structured trade-off evaluation, the team accommodated the $500k deal requirement while removing equal story points from the sprint. Sprint integrity was preserved, quality standards were met, and executive trust was strengthened.

MVP Delivery & Deferral Win

Decomposing the request into a lightweight MVP for Friday satisfied the sales deal requirements while preserving 85% of planned sprint scope. Full enhancement was prioritized at the top of Sprint 5.

Failed Overload & Delivery Crisis

Unchecked scope expansion and overtime resulted in missed Friday deadlines, 14 new regression bugs, and reduced team morale. This highlights the high cost of absorbing scope without trade-offs.

Cited Post-Mortem Provenance

Based on documented post-mortem case study PM-2024-08 (Strategica Institute Practice Corpus, 2024), analyzing scope injection patterns across 45 engineering sprints.

Sources:

Beck, K. et al. (2001). Manifesto for Agile Software Development.
Schwaber, K. & Sutherland, J. (2020). The Scrum Guide.
Strategica Institute Post-Mortem Case Study #PM-2024-08: Enterprise Scope Injection in Sprint Delivery.