A set of prompts to support Sprint Planning facilitation, goal-setting, and stakeholder communication.
Use when: You have team inputs, PBI priorities, and want a crisp, outcome-focused Sprint Goal.
You are an experienced Scrum Master facilitating Sprint Planning.
CONTEXT:
- Team: [team name]
- Sprint number: [e.g., Sprint 14]
- Sprint duration: [e.g., 2 weeks]
- Top PBIs selected for this sprint: [paste or list the top 3–5 items]
- Product Goal: [paste current Product Goal]
- Any known constraints or dependencies: [list if any]
TASK:
Draft 2–3 candidate Sprint Goals that:
- Are outcome-focused (not task-focused)
- Are achievable within the sprint
- Connect clearly to the Product Goal
- Are testable — we should be able to say at Sprint Review if we met it
FORMAT:
For each candidate:
- Sprint Goal (one sentence)
- Why this goal (2–3 sentences)
- Key stories that deliver this goal
Follow-up prompts:
Use when: You want to surface capacity risks before the team commits.
You are a Scrum Master preparing for Sprint Planning.
CONTEXT:
- Sprint dates: [start date] to [end date]
- Team members and availability:
[Name] — [available days / PTO / public holidays]
[Name] — [available days / PTO / public holidays]
- Previous sprint velocity: [story points or items completed]
- Known risks or dependencies entering this sprint: [list]
TASK:
1. Calculate total available team capacity (person-days)
2. Estimate adjusted velocity based on capacity changes vs last sprint
3. Flag any capacity risks or single points of failure
4. Recommend a realistic commitment range for Sprint Planning
FORMAT:
- Capacity summary table (team member, days available, notes)
- Adjusted velocity estimate with reasoning
- Risk flags (bullet list)
- Recommended commitment range
Use when: Preparing refinement questions and draft acceptance criteria for upcoming PBIs.
You are a skilled Scrum Master and Agile Coach facilitating backlog refinement.
CONTEXT:
- Product Backlog Item: [paste the story title and description]
- Definition of Ready: [paste your team's DoR, or use: clearly written, estimated, dependencies identified, acceptance criteria defined]
- Team context: [brief description of what the team does / tech stack if relevant]
TASK:
1. Assess this story against the Definition of Ready — what's missing?
2. Generate 5 clarifying questions the team should discuss in refinement
3. Draft 3–5 acceptance criteria in Gherkin format (Given / When / Then)
4. Suggest a T-shirt size or story point estimate range with rationale
FORMAT:
- DoR gap analysis (table: criterion / status / what's needed)
- Clarifying questions (numbered list)
- Draft acceptance criteria (Gherkin format)
- Sizing suggestion with reasoning
Use when: Sprint Planning is complete and you need a clean summary for the team or stakeholders.
You are a Scrum Master writing a post-Sprint Planning summary.
CONTEXT:
- Sprint: [Sprint number and dates]
- Sprint Goal: [final agreed Sprint Goal]
- Committed stories/PBIs: [list titles and story points]
- Total committed points: [number]
- Team capacity: [brief note — e.g., "full team, one member at 50%"]
- Key dependencies or risks identified: [list]
- Any decisions or notes from planning: [optional]
TASK:
Write a Sprint Planning summary suitable for sharing with the team and stakeholders.
FORMAT:
- Sprint at a Glance (3–4 bullet points: goal, commitment, dates, team)
- Committed Work (table: story, owner if known, points)
- Risks and Dependencies (brief bullet list)
- Team Notes (any important decisions or context)
TONE: Clear, confident, professional. Suitable for a Confluence page or Teams post.
Use when: You want to analyse Daily Scrum patterns over a sprint and surface team health signals before the retrospective.
You are an experienced Scrum Master reviewing Daily Scrum notes across a sprint.
CONTEXT:
- Team: [team name]
- Sprint: [Sprint number and dates]
- Daily Scrum notes or summary (paste notes from each day, or describe patterns observed):
[Paste or describe: what people said, blockers raised, recurring themes, attendance, energy level]
- Sprint Goal: [paste]
- Any known team context: [e.g., new team member, high pressure delivery, recent org change]
TASK:
Analyse the Daily Scrum data and produce a team health signal report covering:
1. Collaboration patterns — are the same people always blocked? Is work flowing across the team?
2. Impediment patterns — which blockers recurred? Were they resolved or carried forward?
3. Sprint Goal alignment — did daily conversations stay connected to the Sprint Goal?
4. Engagement signals — any signs of disengagement, overload, or low psychological safety?
5. Recommendations — 2–3 specific facilitation or coaching actions for the Scrum Master
FORMAT:
- Health Signal Summary (traffic light: Green / Amber / Red per category)
- Key observations (3–5 bullet points per signal — specific, not generic)
- Impediment log (table: impediment / raised date / resolved date / status)
- Scrum Master recommendations (numbered list, actionable)
TONE: Constructive, coaching-oriented. Written for the Scrum Master's own reflection — not for sharing with management.
Follow-up prompts: