Plan a Sprint Retrospective with Timed Steps, Questions and a Dot-Vote
Get a retro format matched to your team's mood and problems, with a timed agenda, warm-up, open questions, and a dot-vote that ends in at most three owned actions.
You getFormat chosen and why, timed agenda table and retro questions
Prompt
Act as an experienced agile coach who runs sprint retrospectives for software teams.
Your job: design a retrospective for my team, including the questions and a timed facilitation plan.
Before you start, ask me these questions in one message and wait for my answers:
1. How many people will attend, and is it remote, in person or hybrid?
2. How long is the retro, and how long was the sprint?
3. What is the team's mood right now (tired, frustrated, upbeat, quiet)?
4. What went wrong or caused friction this sprint?
Rules:
- Pick one retro format that fits the mood and problems, and explain in two sentences why you chose it over one named alternative.
- Every step has a time in minutes, and the times add up exactly to the total length I gave.
- Include a warm-up under 5 minutes that does not force anyone to share personal feelings.
- Write 4-6 open questions; none can be answered yes or no, and none blames a person.
- End with a dot-vote that produces at most three actions, each with one owner and a check-in date.
Output format:
1. Format chosen and why
2. Timed agenda table: Step | Minutes | What the facilitator says or does
3. Retro questions (numbered)
4. Dot-vote instructions
5. Blank action table for the room: Action | Owner | Check-in date
6. Three facilitator tips for this team's mood
Finish with one line on what could derail this retro and how to handle it.Example output
Tips and common edits
Why this works
- Asking about mood and recent problems first lets the model pick a format that fits instead of defaulting to start/stop/continue.
- Requiring minutes that add up to the real retro length makes the agenda usable as a live run sheet.
- Capping actions at three with named owners stops retros from ending in a long wish list nobody follows up on.
Use before your next sprint retro. Have the headcount, retro length, an honest read of team mood and the sprint's main problems ready. Works in ChatGPT, Claude or Gemini.
Common edits
- Ask for a 30-minute version for short sprints or teams with heavy meeting load.
- Request the questions formatted as sticky-note prompts for Miro, FigJam or a whiteboard.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Run a Brainstorming Meeting That Ends with Chosen Ideas and Owners
You get a timed brainstorming agenda with silent ideation, clustering and dot voting, plus idea prompts, ending with top ideas, owners and a next test.
Build a RACI Chart from Your Project Task List with Ownership Gaps Flagged
Turns a pasted task list into a RACI table with one Accountable per task, flags unowned or over-consulted tasks, and lists questions to confirm with your team.
Build a Timed Meeting Agenda with Owners, Decision Labels and Pre-Reads
Get a timed agenda where every item has a Decide, Discuss or Inform label, an owner and minutes that fit the slot, plus pre-reads and a list of items to handle async.
Draft a Hard Team Announcement for a Reorg, Delay or Policy Change
Get a clear team announcement that states the news first, shows what changes and stays the same for each group, and answers likely questions honestly.
Write a Project Kickoff Message for Your Team and Stakeholders
You get a short team kickoff message covering why, scope, roles, first deadline and questions, plus a shorter stakeholder version and a list of gaps.
Build a Reusable Report or Memo Template Anyone on Your Team Can Fill In
Get a blank document template with headed sections, one-line guidance under each, a fully filled example, and a short pre-send checklist.