20%12 min
Metrics review
Look at what the sprint produced: finished work, carry-over, cycle time and incidents. Facts come first, so the discussion starts from one shared picture.
🔁 Retrospectives
Sprint retrospective agenda with time blocks
A retro without time blocks spends the whole hour on the first complaint. This 20/50/30 split gives metrics, improvements and action items their own timer, and HuddlePace runs the clock inside your Slack Huddle.
- 60-minute template
- Runs in a Slack Huddle
- 0% audio recorded
The 20/50/30 split
Here is how 60 minutes divide. Change the total in the modal and the minutes follow the percentages.
50%30 min
Improvement discussion
Pick the two or three topics the team cares about most and work them properly. Thirty minutes covers a few topics well and ten topics badly.
30%18 min
Agreements and action items
Turn the discussion into commitments. Every item gets an owner and a date before this block ends.
Four ways a retro goes off the rails
The first topic eats the hour
A visible bar tells the room how much of the block is left, so nobody has to be the person who interrupts.
Metrics turn into a debate
Twelve minutes is enough to read the numbers. Arguments about causes belong to the discussion block.
Action items arrive in the last two minutes
Giving them 30% of the time puts them on the clock instead of the leftovers.
Everyone leaves with a different list
The Huddle thread stays open, so the team can write the action items where everyone sees them.
Run it in three steps
- 1
Open the modal
Type
/pacein the channel where your team holds the retro. - 2
Enter the three modules
Set 60 minutes and the percentages 20, 50 and 30. HuddlePace checks that they add up to 100.
- 3
Save it as a template
Tick Save as template. Next sprint you start from the saved agenda in one click.
What the team sees in the Huddle thread
HuddlePaceAPPSprint retro
Active module: Improvement discussion
⏭️ Next up: Agreements and action items
- Live progressThe bar updates every 30 seconds with the current topic and the time left.
- Private nudgesThe active speaker gets a Slack DM at the midpoint and with one minute left.
- Time that movesFinish early, tap Next Module and the spare minutes go to the next block.
Facilitator tips
Protect the last block
It is the block that turns the retro into change. Cut the discussion before you cut this one.
Compare sprint to sprint
Run /pace report 30 to see how closely your retros followed their timebox.
Retrospective questions
How long should a sprint retrospective be?
The Scrum Guide caps it at three hours for a one-month sprint and treats it as shorter for shorter sprints. Many two-week teams use 60 minutes. The percentages scale to any length.
Can I change the percentages?
Yes. Set any split in the schedule modal. The modules must add up to 100%, and when you edit one value HuddlePace rebalances the others.
What happens if a block finishes early?
The speaker taps Next Module and the leftover time moves to the next block.
Does HuddlePace record the retro?
No. It records 0% audio and keeps only the timestamps and the agenda modules it needs to run the timer.
Run your next retro on the clock
Install HuddlePace, run /pace and save the agenda as a template.
Early access, free today. Pricing will be per workspace, never per user, and the features available today stay free.