Standup Order Randomizer
Picks today's scrum standup order.
Built and maintained by Paul Clark, Redmoon Software · Last checked
This tool sets a fresh random speaking order for your daily scrum standup and saves your team locally so it's ready each morning. No more defaulting to the same person every day or talking over each other. You can also skip anyone who's out before you shuffle.
Add. Enter your team members once; they're saved locally for next time.
0 items
Click Today's standup order to see a result.
Options
Recent results
- No history yet.
How it works
- Add. Enter your team members once; they're saved locally for next time.
- Skip. Uncheck anyone who's absent today in Options.
- Shuffle. Click "Today's standup order" to get a fresh random lineup.
About the Standup Order Randomizer
What the minutes column actually shows
Set Per-person minutes and each name gets a time beside it. That number is the point at which that person should be finished, not the point at which they start — the first name shows one interval, the second shows two, and so on. Read the last line and you have the projected end of the standup, which is the number worth looking at.
It is a projection and nothing more. There is no timer, no alert and no connection to the clock; the tool has no idea when you actually started or whether the third person is still talking. The value is in seeing, before you begin, that eleven people at two minutes each is a twenty-two minute standup — which is usually the moment somebody suggests two minutes is optimistic.
Why re-rolling every day is the whole idea
A standup that runs in a fixed order — alphabetical, by seniority, by whoever set up the board — gives the same person the last slot every single day. That is the slot where attention has drained and where "we are over time, be quick" lands. Over a year it is a real, compounding disadvantage that nobody chose and nobody notices.
Each run is an independent shuffle with every ordering equally likely, so the tool has no memory of yesterday and makes no attempt to give people turns at the front. Somebody will go last twice in a row, and occasionally three times; that is what randomness looks like, and it is still fairer than a fixed order. If you want a strict rotation instead, a sequential no-repeat picker is the right tool.
Keeping the daily habit honest
- Paste the people who are actually present. A shuffle including three people on leave produces a schedule that is wrong from the first name.
- The list persists in your browser, so the daily job is deleting the absentees rather than retyping the team.
- Set the minutes to what your standup really takes, not what you wish it took. The projection is only useful if it is honest.
- For an ordering you need to justify later — a rotation people are watching — use a tool that accepts a seed. This one draws fresh every time and cannot be replayed.
Frequently asked questions
Does it remember my team?
Yes. Your team list is saved locally in your browser, so it loads automatically the next time you open the tool.
How do I skip someone today?
Open Options and uncheck anyone who's absent, then generate the order so only the people present are included.
Is the order really random?
Yes. Each morning's lineup is shuffled with your browser's crypto.getRandomValues, so it's a genuinely fair order rather than a fixed rotation.
Is my saved team data private?
Yes. The team list is stored only in your browser's local storage and is never uploaded to any server.
Related randomizers
Further reading
- Save the 'deep' questions for your 1:1s, not the standup
A daily-question generator isn't just for the team channel. Here's how the 'deep' category becomes a manager's best warm-up for a one-on-one — and why the same question lands completely differently in private.
- Which retro format fits the sprint you actually had
Rotating retro formats keeps them fresh, but some sprints call for a specific shape. Here's a facilitator's guide to matching the format to what really happened — a rough sprint, a smooth one, a big milestone, or a team that's gone quiet.
- Stop running out of questions for the team's daily channel
Every #random or #watercooler channel starts strong and quietly dies when the same person runs out of things to ask. Here's how a random question of the day — rotated across work, fun, and deep categories — keeps it going without anyone owning it.
- Format fatigue is why your retros are getting quieter
Start/Stop/Continue was great for the first ten sprints. Now the board fills up in silence and half the team says 'same as last time.' Here's the real failure mode behind quiet retros — and how rotating formats fixes it.
- Why every candidate for the same role should get the same random question set
Comparing candidates only works if you asked them the same things. Here's the case for a seeded random draw of interview questions — consistent enough to score fairly, varied enough to avoid a rehearsed script.
- Does it just feel unfair, or is it? Audit your random picks over time
One person swears they get picked for chores twice as often as everyone else. With a randomizer that logs every draw and exports to CSV, you don't have to argue about feelings — you can open the spreadsheet and count.
- Run a demo day that actually ends on time
Sprint reviews fail two ways: the order argument at the start and the overrun at the end. A random demo order with a built-in schedule — every team slotted into minuted time boxes — fixes both in one click.
- Randomizing your presentation order (and giving every slot a clock)
Whoever goes first at a demo day, sales pitch, or classroom presentation gets an unfair edge — or an unfair disadvantage. Here's how a random presentation order generator settles the lineup and keeps every speaker on time.
- Why your standup always starts with the same person (and how to fix it)
The daily standup has a quiet bias: whoever's at the top of the list goes first every day. Here's why fixed order hurts your standup, and how a thirty-second shuffle changes the whole meeting.