Retrospective Workshop Designer
Design engaging sprint retrospectives with collaborative activities, voting and measurable actions.
Act as an experienced Scrum Master, Agile Coach and retrospective facilitator.
Design a retrospective workshop using the following information.
Team context:
{{team_context}}
Sprint or delivery period:
{{sprint_context}}
Known successes:
{{successes}}
Known challenges:
{{challenges}}
Available time:
{{duration}}
Number of participants:
{{participant_count}}
Previous retrospective actions:
{{previous_actions}}
Create:
1. Retrospective Objective
2. Recommended Retrospective Format
3. Facilitator Preparation
4. Digital Board Structure
5. Opening Check-In
6. Data-Gathering Activity
7. Insight-Generation Activity
8. Prioritization and Voting Method
9. Root-Cause Discussion
10. Action-Planning Activity
11. Closing Check-Out
12. Detailed Agenda With Timings
13. Facilitation Questions
14. Psychological-Safety Guidance
15. Risks and Difficult Situations
16. Expected Outputs
17. Follow-Up Method
18. Measurement of Action Effectiveness
Select a retrospective format appropriate to the circumstances, such as:
- Start, Stop, Continue
- Mad, Sad, Glad
- Sailboat
- Four Ls
- Lean Coffee
- Timeline Retrospective
- Starfish
- Team Radar
- Energy Levels
- Appreciation Retrospective
Do not automatically use the same format every time.
Avoid assigning blame to individuals.
Focus on:
- Systems
- Processes
- Collaboration
- Communication
- Quality
- Flow
- Sustainable improvement
Ensure that every action item has:
- Action
- Owner
- Target Date
- Expected Outcome
- Success Measure
- Review Point
Limit the final action plan to one to three realistic actions.
Format the board so it can be recreated in Collaboard, Miro, Mural, FigJam, Confluence Whiteboards or another collaborative tool.
Return:
1. Facilitator-ready agenda
2. Board layout
3. Instructions for participants
4. Voting method
5. Action template
6. Follow-up planWorks with ChatGPT, Claude, Gemini and Copilot.
Example in action
See how this prompt transforms a real input into a structured result.
Team context: A cross-functional product team with eight participants working remotely. Sprint context: The sprint goal was achieved, but the release was delayed by two days. Known successes: - Development completed the planned scope. - Automated regression tests detected two important defects. - Product and engineering collaborated well during refinement. Known challenges: - QA received several stories late in the sprint. - Environment instability delayed testing. - One dependency was discovered after implementation started. Duration: 75 minutes. Previous retrospective actions: Introduce a mid-sprint dependency review. The action was completed but not measured.
Recommended Format: Sailboat Retrospective Reason: The team achieved the sprint goal but experienced flow and dependency problems. The Sailboat format helps separate supporting factors, risks and obstacles. Board Sections: 1. Destination What outcome was the team trying to achieve? 2. Wind What helped the team move forward? 3. Anchors What slowed delivery? 4. Rocks What risks could affect the next sprint? 5. Actions What will the team change? Agenda: 00:00–00:05 Welcome and psychological-safety reminder 00:05–00:12 Check-in: one word describing the sprint 00:12–00:27 Silent contribution to the Sailboat board 00:27–00:37 Group related observations 00:37–00:47 Dot voting: three votes per participant 00:47–01:02 Root-cause discussion for the top two topics 01:02–01:12 Create one to three actions 01:12–01:15 Closing check-out Primary Action: Action: Introduce a Ready for QA entry check before a story leaves development. Owner: QA Lead and Development Lead Expected Outcome: Fewer incomplete stories reach QA late in the sprint. Success Measure: At least 90% of stories entering QA meet the agreed checklist. Review Point: Next retrospective.