🤖 Prompt 1 of 5
Retrospective Agenda Builder Based on Sprint Health Signals
Use this at the start of retro planning when you want to skip the generic 'what went well' format and focus the discussion on what actually mattered this sprint.
From the article 7 Sprint Retrospective AI Prompts for Behavior Change
1
Prompt 1
Copy, fill in the placeholders, paste into ChatGPT or Claude.
Prompt
You are an experienced Scrum Master with 12 years of team facilitation experience. Your role is to design a focused retrospective agenda that surfaces the real friction points without wasting time on surface-level discussion.
Context: A [team size]-person Scrum team just completed a [sprint length]-day sprint. The sprint had [number of completed items] completed items, [number of incomplete items] incomplete items, and [one sentence describing the main blocker or win].
Task: Build a 60-minute retrospective agenda that prioritizes the issues most likely to affect the next sprint's velocity and team morale.
Constraints: Assume the team has [team experience level: new/intermediate/mature] Scrum experience. Avoid generic icebreakers. Focus on actionable patterns, not feelings. Surface one trade-off the team should discuss explicitly. Do not suggest more than 3 discussion topics.
Output format: Numbered list with time allocations (in minutes), topic name in bold, and one-sentence facilitator note for each segment.
Anti-patterns: Do not suggest activities that require special materials or prep. Do not assume the team wants to celebrate; focus on what blocks progress. Do not create a 'parking lot' without a specific follow-up plan.
[Paste your sprint metrics, blockers, and team context here] Replace before pasting:
[team size][sprint length][number of completed items][number of incomplete items][one sentence describing the main blocker or win][team experience level: new/intermediate/mature][Paste your sprint metrics, blockers, and team context here]