One Retro Format That Works for Most Teams

If you had to choose one retrospective format for ordinary sprint work, choose Plus/Delta.

It is also known as What Went Well and What Could Improve. The format is almost boring on purpose:

• Plus: what went well, and what should we keep doing?
• Delta: what should change, and what should we try next?

The shape is deliberately plain: two columns, clear notes, a short discussion, and one or two action items.

For many teams, that is enough.

Why Plus/Delta holds up

A good default retro format should be easy to explain, quick to run, and strong enough to create useful actions. Plus/Delta does those jobs without asking the team to learn a new exercise every sprint.

It lowers the instruction cost

Some formats need a story before anyone can contribute. The boat is the project, the anchor is the blocker, the wind is the support, the island is the goal.

Those formats can be useful at the right moment. They are not always needed for a normal sprint.

Plus/Delta needs almost no explanation. People can start writing straight away.

It balances the room

A retro that only covers problems can become draining. A retro that only celebrates wins can avoid needed change.

Plus/Delta gives both sides space.

The Plus column asks the team to notice what should continue. The Delta column asks what needs to change. That balance matters because teams need to repeat good behaviour as well as fix weak spots.

It points naturally to action

A Delta note should lead to a next step.

• "Reviews took too long" can become "Agree a pull request review rota by Tuesday."
• "Planning missed a dependency" can become "Add a dependency check to sprint planning."
• "Release notes were late" can become "Draft release notes two days before release."

The format does not solve the issue by itself, but it makes the next conversation easier.

It gets better with repetition

Once the team uses the same default format, it gets faster. People know what kind of notes help. The facilitator spends less time teaching and more time guiding the discussion.

Repetition is not the enemy. Mindless repetition is.

Keep the format steady. Improve the questions, the facilitation, and the follow-up.

How to run a Plus/Delta retro

Use this flow for a 30 to 45 minute sprint retrospective.

1. Review last sprint's actions

Start by checking the previous commitments. Done, not done, or still useful?

Keep this calm and short. The review is there to build trust in follow-through.

2. Write notes silently

Give everyone a few minutes to add Plus and Delta notes. Silent writing stops the first speaker from setting the whole direction.

Ask for specific notes rather than slogans.

• Weak: Communication was bad.
• Better: Backend API changes were not shared before frontend planning.

3. Group similar notes

Put repeated themes together. Do not overthink the labels. The goal is to see what the team keeps mentioning.

4. Discuss the highest-value themes

Pick the themes that would make next sprint easier if addressed. Avoid spending the whole retro on a topic the team cannot change.

5. Create one or two actions

Each action needs an owner and a date. If an action has no owner, it is not an action. If it has no date, it is not a commitment.

6. Share the summary

End with a short summary of the themes and actions. If the team uses Slack, share it there. If the team plans in Jira or Linear, add the actions there.

SprintPulse follows this shape: Plus/Delta boards, smart merge for repeated notes, AI summaries, suggested action items, and two-way Jira and Linear sync. It keeps the format simple and puts the effort into follow-up.

When Plus/Delta is not enough

A default format should not become a cage. There are moments when another exercise fits better.

Use something else when:

• The team has just had a serious incident and needs a timeline or 5 Whys.
• The sprint carried a lot of emotion and Mad Sad Glad would help people name it.
• The team is new and an appreciations exercise would help people learn how others work.
• You are doing a quarterly health check and want a wider view than one sprint.

Use the special format for that meeting, then return to your default if it still serves the team.

The format is only half the work

A simple retro format will not save poor follow-up.

Plus/Delta works if the team uses it to make decisions. It fails if the team fills two columns, talks for a while, and leaves without a clear next step.

If you use Plus/Delta, protect the final ten minutes. That is when the retro earns its time.

Choose the action. Name the owner. Set the date. Put it where the team will see it.

The board can be simple. The follow-up cannot be optional.