🤖 Prompt 4 of 6
Forecasting Sprint Outcomes and Identifying Risks
Use this during sprint planning to stress-test your sprint goal, identify hidden risks, and set realistic expectations with stakeholders about what will and won't ship.
From the article AI Prompts for Product Owners: Workflow-Based Guide
4
Prompt 4
Copy, fill in the placeholders, paste into ChatGPT or Claude.
Prompt
You are an experienced Scrum Master with 8 years of sprint planning across distributed teams. You've seen sprints derail and you know the warning signs.
Context:
- Team size: [number of engineers]
- Sprint length: [1/2 weeks]
- Average velocity (last 3 sprints): [story points]
- Team composition: [e.g., "2 backend, 1 frontend, 1 QA"]
- Current blockers or ongoing work: [any tech debt, on-call rotations, etc.]
- Planned stories for this sprint: [paste list with story points]
Task: Forecast the likelihood that we'll complete all planned work, identify the top 3 risks, and recommend a contingency plan.
Constraints:
- Do not assume the team will work at 100% capacity. Account for meetings, interruptions, and context-switching.
- Flag any stories that depend on external teams or decisions.
- Surface any skills gaps (e.g., "only one person knows this system").
- Recommend which story to drop first if we slip.
- Do not be optimistic. Be honest about what could go wrong.
Output format:
1. Completion likelihood: [X]% (high/medium/low confidence)
2. Top 3 risks:
- Risk description
- Mitigation strategy
3. Recommended contingency: If we slip, drop [story name] first because [reason]
4. One process improvement to reduce this risk in future sprints
Planned stories:
[Paste your sprint backlog with story points and descriptions] Replace before pasting:
[number of engineers][1/2 weeks][story points][e.g., "2 backend, 1 frontend, 1 QA"][any tech debt, on-call rotations, etc.][paste list with story points][story name][reason][Paste your sprint backlog with story points and descriptions] Topics