🤖 Prompt 4 of 5
Mid-Sprint Check-In
Use it when you sense something is slipping or when stakeholders are asking if you'll make the goal.
From the article 7 ChatGPT Prompts for Sprint Progress Visualization That Actually Work
4
Prompt 4
Copy, fill in the placeholders, paste into ChatGPT or Claude.
Prompt
You are a Scrum Master who excels at mid-sprint course correction. You help teams see reality clearly and adjust scope or approach without abandoning their goal.
Context: We are a [team size]-person team. We're on day [current day] of a [sprint length]-day sprint. Our sprint goal is [sprint goal]. Our team's velocity over the last three sprints was [past velocities: e.g., "32, 35, 30 story points"].
Task: Analyze our mid-sprint progress, compare it to our plan, and surface what needs to change to hit our goal.
Constraints:
- Identify work that's at risk of not completing
- Surface scope creep or unplanned work that entered the sprint
- Recommend specific adjustments (reduce scope, add resources, change approach)
- Do not assume we'll "just work harder" to make up time
- Flag any external dependencies that are blocking progress
Output format: Provide a structured analysis with these sections:
1. **Progress vs. Plan** (% of planned work completed by day [current day], expected % at this point, variance)
2. **At-Risk Work Items** (tasks that are likely to slip, ranked by impact on sprint goal)
3. **Scope Creep Assessment** (any unplanned work that entered the sprint, its impact)
4. **Recommended Actions** (3-5 specific changes to increase likelihood of goal completion)
5. **Stakeholder Conversation** (what to say to product leadership if you're behind)
Anti-patterns to avoid:
- Do not assume all tasks are equally important
- Do not recommend working weekends or skipping other commitments
- Do not hide bad news; surface it clearly
[Paste your current sprint board status, including task completion, in-progress work, and any blockers here] Replace before pasting:
[team size][current day][sprint length][sprint goal][past velocities: e.g., "32, 35, 30 story points"]