Skip to content

Latest commit

 

History

History
51 lines (36 loc) · 1.49 KB

File metadata and controls

51 lines (36 loc) · 1.49 KB

Stakeholder update

Category: Sprint review
Purpose: Produce a concise sprint update for leadership.


When to use

After Sprint Review or at any point during the sprint when leadership need a status update — especially useful for distributed or async teams.


Prompt

You are an Agile Coach writing a sprint update for senior leadership.

Sprint: [SPRINT_NUMBER] | Team: [TEAM_NAME]
Sprint goal: [SPRINT_GOAL]
Goal achieved: [YES / NO / PARTIALLY]
Stories completed: [COUNT] of [COUNT_COMMITTED] ([POINTS] points)
Key deliverables: [LIST_KEY_DELIVERABLES]
Metrics: [VELOCITY, QUALITY_INDICATORS, etc.]
Next sprint focus: [NEXT_SPRINT_HEADLINE]

Write a crisp leadership update (100–150 words) in a confident, factual tone. Include a traffic-light status (Red / Amber / Green) with a one-line justification.

Placeholders

Placeholder What to fill in
[SPRINT_NUMBER] e.g. Sprint 14
[TEAM_NAME] Your team's name
[SPRINT_GOAL] The agreed Sprint Goal
[GOAL_ACHIEVED] Yes / No / Partially
[COUNT] of [COUNT_COMMITTED] e.g. 7 of 8 stories
[POINTS] e.g. 38 story points
[LIST_KEY_DELIVERABLES] 2–3 headline deliverables
[METRICS] Velocity, defect count, test coverage etc.
[NEXT_SPRINT_HEADLINE] One-line focus for next sprint

Follow-up prompts

  • "Convert this into a Teams/Slack message under 100 words."
  • "Add a risk section highlighting the top 2 concerns going into next sprint."