Made for Engineering Managers
Send a Sprint Risk Update Stakeholders Can Act On
Also useful for: people in Engineering Managers, people in Software Engineering Managers
15 min
Beginner
Engineering Managers
Engineering Manager
Become a Better Manager
Career outcome:
Avoid Professional Risk
Convert active sprint risk into a clear update that helps stakeholders choose a tradeoff instead of debating the status.
Create a free account to save your progress and use this Playbook.
Use this when
A sprint commitment is at risk and stakeholders need a clear forecast, business impact, realistic options, and a decision before the situation gets worse.
You'll need
- Sprint goal
- Stakeholder audience
- Current forecast
- Risk evidence
- Business impact
- Tradeoff options
- Decision request
You'll get
- A current forecast stated without false precision
- Evidence clearly separated from assumptions
- Business impact tied to the sprint goal
- At least two viable tradeoff options
- One recommended option
- One decision request with an owner and deadline
By the end of this playbook
You will have:
- A current forecast stated without false precision
- Evidence clearly separated from assumptions
- Business impact tied to the sprint goal
- At least two viable tradeoff options
- One recommended option
- One decision request with an owner and deadline
Sample
This is sample data, not your prompt. Pro unlocks this higher-stakes Playbook. On Free Playbooks you can still copy the assembled prompt into any AI.
Sample input
Sprint goal: Launch self-service password resets before the May 6 support rollout. Audience: Product director and support lead; the product director owns scope. Forecast: Core reset flow should finish this sprint. The admin override is likely to slip by three to five business days. Evidence: Two security tests failed. Eight points remain with three engineering days left. The two-day fix estimate is still an assumption. Impact: Support can launch, but locked accounts will need manual escalation until the override ships. Options: Move the override to the next sprint; delay the full launch; add an engineer and disrupt billing work. Decision: Product director approval to move the override, needed by 2 PM tomorrow.
Sample assembled prompt
Risk check: The current forecast depends... State it as a range and... Subject: Decision needed tomorrow: password reset... Two security tests failed, eight points... The current range assumes the security... If the override slips, support can... Options: 1. Move the admin override to the... This protects the May 6 launch... 2. Keep full scope and delay... This avoids the manual process but... 3. Reassign an engineer from billing. This may reduce the delay but... I recommend option 1 because it... Product Director: Please approve moving the...