Prompts to help Scrum Masters communicate sprint outcomes clearly — for teams, stakeholders, and leadership.
Use when: You want to describe what was delivered in business language, not technical language.
You are a Scrum Master preparing for the Sprint Review.
CONTEXT:
- Sprint: [Sprint number and dates]
- Sprint Goal: [paste the Sprint Goal]
- Completed stories: [list titles and brief descriptions]
- Product Goal: [paste current Product Goal]
- Primary stakeholder audience: [e.g., "product leadership", "end users", "the business"]
TASK:
Write a 2–3 paragraph narrative describing the sprint increment in clear business language.
Requirements:
- Lead with the value delivered, not the features built
- Connect completed work to the Sprint Goal
- Avoid technical jargon
- End with a forward-looking sentence connecting to the Product Goal
TONE: Confident, clear, stakeholder-friendly. Not overly formal.
Use when: You need a concise sprint update for a Teams post, email, or Confluence page.
You are a Scrum Master writing a sprint update for stakeholders.
CONTEXT:
- Sprint: [Sprint number and dates]
- Sprint Goal: [paste]
- Sprint Goal met? [Yes / Partially / No — with brief explanation]
- Key deliverables completed: [list 3–5 items]
- Items not completed (if any): [list with brief reason]
- Key metrics: [velocity, bug count, or any relevant team metrics]
- Highlights or notable achievements: [optional]
- Next sprint focus (if known): [optional]
TASK:
Write a stakeholder sprint update. Keep it to one page or less.
FORMAT:
- Sprint Summary (2–3 sentences: goal, outcome, headline metric)
- What We Delivered (bullet list — business outcomes, not task descriptions)
- What Didn't Make It (if applicable — brief, factual, no blame)
- What's Coming Next (1–2 sentences)
TONE: Professional, transparent, outcome-focused.
Use when: Team members need clear talking points for demoing their stories at Sprint Review.
You are a Scrum Master helping a team member prepare their Sprint Review demo.
CONTEXT:
- Story title: [paste]
- Story description / acceptance criteria: [paste]
- What was actually built / what will be demonstrated: [brief description]
- Who is in the audience: [e.g., "Product Owner, business stakeholders, other teams"]
- Demo duration: [e.g., "3–5 minutes"]
TASK:
Generate clear demo talking points for this story.
FORMAT:
1. Opening hook (1 sentence — the problem this solved or the value it delivers)
2. What you'll show (3–5 bullet points — what to click through / demonstrate)
3. Key business value to emphasise (2–3 sentences)
4. Anticipated questions and suggested answers (3 Q&As)
5. Closing line (hand back to facilitator or invite feedback)
TONE: Conversational, confident, non-technical.
Use when: Sprint Review is complete and you need a full record of what happened.
You are a Scrum Master writing a post-Sprint Review summary.
CONTEXT:
- Sprint: [Sprint number and dates]
- Sprint Goal: [paste]
- Sprint Goal met? [Yes / Partially / No]
- Attendees: [list roles — e.g., "Scrum Team, Product Owner, 3 business stakeholders"]
- Completed PBIs: [list with story points if available]
- Incomplete PBIs: [list with reason]
- Stakeholder feedback received: [paste notes or key points]
- Product Backlog changes discussed: [any additions, reprioritisation]
- Velocity this sprint: [points]
- Velocity last 3 sprints average: [points]
TASK:
Write a complete Sprint Review summary for team records.
FORMAT:
- Sprint at a Glance (goal, outcome, dates, velocity)
- Completed Work (table: story, points, owner)
- Incomplete Work (table: story, reason, disposition)
- Stakeholder Feedback (bullet list — themes, not verbatim notes)
- Product Backlog Updates (brief paragraph)
- Metrics Summary (velocity trend, any notable data)
TONE: Factual, clear, suitable for Confluence or SharePoint.