WRAP Retrospective

WRAP gathers four kinds of input that together give a rounded view of the sprint. The team shares its wishes, voices appreciations, names the risks it sees and surfaces the things that still puzzle it. Mixing gratitude with concern keeps the conversation both supportive and honest.

😇 What are your wishes?

What you want for the team going forward

Roman

One protected day a week without meetings

Maria

Tickets that arrive with acceptance criteria

🤗 What do you appreciate?

Credit for people whose work made yours easier

Anna

Ana picked up the 3am page and wrote the incident up by morning

Daria

Support wrote workarounds that saved us two escalations

😨 What risks do you see?

Risks you can see coming that nobody is handling yet

Maria

Peak season load is untested

Kirill

Only one person can maintain billing

😵 What things are puzzling you?

Things that do not add up and deserve a closer look

Daria

Why the same three tickets roll over every sprint

Roman

Whether the reports feature is used at all

Try Template

What is the WRAP retrospective?

The WRAP retrospective is a well-rounded closing format that balances forward-looking wishes, positive recognition, honest risk-spotting, and open questions. The name comes from its four columns — Wishes, Appreciations, Risks, and Puzzles — and the format is a natural fit for wrapping up a sprint, a release, or a project phase. By combining gratitude with candor, WRAP keeps morale high while still surfacing the issues that need attention. The format uses four columns:

Wishes — what the team wants to see happen next.
Appreciations — recognition for people and good work.
Risks — concerns and potential problems ahead.
Puzzles — open questions and things the team doesn't yet understand.

Wishes

The Wishes column captures hopes and desired changes for the period ahead — improvements the team would like to see, things they wish they had, or ways of working they want to try. Wishes turn the retro toward the future and feed naturally into action items.

Appreciations

The Appreciations column is dedicated to recognition: thanking teammates, celebrating good work, and naming the moments that made the difference. Explicit appreciation strengthens relationships and reminds the team that progress is a collective effort.

Risks

The Risks column names concerns and potential problems on the horizon: fragile areas, dependencies, or decisions that could backfire. Surfacing risks early gives the team time to plan mitigations rather than react in a crisis.

Puzzles

The Puzzles column holds open questions and unknowns — things the team is unsure about or doesn't yet understand. Capturing puzzles legitimizes uncertainty and creates a clear list of topics to investigate before they become risks.

Benefits of the WRAP retrospective

Balances appreciation with honest concern.
Keeps morale high while surfacing real issues.
Captures open questions instead of forcing premature answers.
Turns wishes directly into action items.
Fits sprint, release, and project closings.
Strengthens team relationships through recognition.

How to run a WRAP retrospective

Create a board in QRetro from the WRAP template and invite your team.
Explain each column and the time period the retro covers.
Give everyone 5–7 minutes to add cards across all four columns.
Start with Appreciations to set a positive tone, then read the others aloud.
Discuss risks and puzzles, and vote on which wishes to act on.
Assign owners to the top items and save the board for follow-up.

Similar templates

Other formats teams pair with this one — open any of them as a board in one click.

Learning Matrix

A four-quadrant format that captures feelings, ideas and gratitude in one view. The team notes what made it smile, what disappointed it, the new ideas worth trying and the appreciations it wants to share. The balanced layout makes it easy to leave the session with both improvements and a sense of recognition.

RAID Log Analysis

A project-management format that puts the spotlight on what could derail delivery. The team logs its risks, the assumptions it's relying on, the issues already in play and the dependencies on other teams or systems. Reviewing all four regularly keeps surprises to a minimum and makes planning conversations far more grounded.

Liked - Lacked - Change Retrospective Template

A reflective format that moves from observation straight to ownership of change. The team names what it liked and what it lacked, then splits change into two columns — what each person can do differently and what the team can change together. Separating personal and collective action makes the resulting commitments clearer and more actionable.

Time: Added Stolen Restored

A reflective format that examines how the team and its members spend their most limited resource — time. Participants look at the choices that add time to the day, the habits that steal it and the ways to reclaim what's been lost. It's a personal, mindful angle on productivity that goes beyond process and into working habits.

Appreciation Retro

A retrospective built around continuous improvement and an empathetic team culture. Alongside the usual reflection on what was good and what fell short, it makes space to wonder, to commit to action items and, above all, to appreciate one another. The strong emphasis on gratitude helps teams ask hard questions without fear and have courageous conversations.

Christmas Retro

A festive retrospective that borrows the spirit of A Christmas Carol. Christmas Past reflects on what could have gone differently, Christmas Present on what's working and the people worth thanking, and Christmas Future on what the team wants ahead — with a lighthearted Foodie column to share favorite treats. A warm, seasonal way to close out the year together.

Try Template