task-ops
Most teams do not need a better daily standup agenda. They need a shorter one. The meeting that started as a two minute huddle now runs twenty five minutes, half the team is muted and looking at something else, and the person running it has started asking for status because nobody can tell what is actually moving.
The agenda is the lever, but not in the way most templates suggest. A template that lists three questions and a time box will not fix a standup that has turned into a reporting line. What fixes it is deciding what the meeting produces. If it produces a plan for the day, it is worth fifteen minutes. If it produces a record of what everyone did yesterday, the board already has that, and the meeting is a duplicate.
The 2020 Scrum Guide is unusually short on this event, and the brevity is the point.
The Daily Scrum is a 15-minute event for the Developers of the Scrum Team. To reduce complexity, it is held at the same time and place every working day of the Sprint. Source: scrumguides.org
The stated purpose is to inspect progress toward the sprint goal and adapt the plan for the coming day. Nothing in that purpose requires each person to speak. Nothing requires a manager to be present. Nothing requires a report.
That matters because the common failure is not a bad agenda but a mismatched audience. The moment someone in the room is there to be informed rather than to replan, every participant starts addressing that person. Sentences get longer. Detail that nobody needs gets added, because the speaker is demonstrating effort rather than surfacing a decision. Once the standup has an audience, it stops being a working session.
The test is simple. At the end of the meeting, ask whether anything about today's work changed. If the answer is no on most days, the meeting is a status broadcast wearing a standup's clothes, and the fix is to delete it and post the same information in writing.
There is a second test worth running. Count how many sentences in the meeting ended with a name and a next action. On a healthy day that number is close to the number of items in progress. On an unhealthy day it is zero, and everyone leaves with exactly the plan they arrived with.
The familiar format asks what was done yesterday, what is planned today, and what is in the way. The current Scrum Guide no longer prescribes those questions, and the reason is visible in any team that still uses them.
Going person by person turns the meeting into a sequence of individual updates. Each speaker covers their own work, which means the listeners hear a lot that does not concern them and miss the one connection that does. Work that is stuck between two people gets described twice, from two angles, and resolved neither time. Work that nobody owns gets described zero times, because there is no person whose turn it is to mention it.
The second problem is that the yesterday question is unfalsifiable and unhelpful. It invites narration. It rewards the person who describes their day well, not the person whose work is closest to done. And because the board already records what moved, the narration is a second copy of the truth that immediately starts to drift from the first.
The third problem is length. Person by person scales with headcount. Eight people at ninety seconds each is already twelve minutes with no time left to decide anything, and ninety seconds is optimistic once questions start.
A useful replacement is to walk the work instead of the people. Start from the item closest to release and move backward toward the item that has not started. For each item, one person says where it is and what happens next. Most people will speak once. Some will not speak at all, and that is a feature, not a sign of disengagement.
The shape below fits inside fifteen minutes for a team of five to ten people working from a shared board.
Minute zero to one: the goal and the calendar. One sentence on what the team is trying to finish this week, and one sentence on anything unusual today. Somebody out sick, a release window, a customer call that will pull two people away. This is the only part that is read out rather than discussed.
Minute one to ten: walk the board from right to left. Take the items in progress in order of how close they are to done. For each one: where it is, what happens next, and who is waiting on whom. Items that moved yesterday and need nothing get a single word. Items that did not move get the question "what would move this today", and the answer is either an action or a blocker.
Minute ten to thirteen: blockers and handoffs. Every blocker gets a name and a date, spoken out loud and written down before the meeting ends. Handoffs get the same treatment. "Review by lunch" is a commitment. "Will look at it at some point" is not, and the person running the meeting should convert the second into the first.
Minute thirteen to fifteen: what changed. Read back the changes to today's plan. Who is switching tasks, what is being dropped, what is being escalated. This takes under two minutes and it is the part most teams skip, which is why people leave the meeting with different pictures of what was decided.
Anything that needs discussion goes on a list and is handled after the meeting by the two or three people it concerns. Naming that list out loud is what keeps the meeting short, because it gives the facilitator a polite place to put a conversation instead of ending it.
Cutting is harder than adding, so it helps to name the categories explicitly.
Leave out yesterday, except where yesterday explains why something is stuck. The board holds the history. Repeating it in the meeting creates a second record that nobody maintains.
Leave out problem solving. The moment two people start designing a fix, the other eight are paying for it. Move it to the list and take the two people with it.
Leave out reading the board aloud. If the meeting consists of someone narrating cards that everyone can see, the meeting is a screen share and can be replaced by a link.
Leave out the roll call. Going around the circle so that everyone has spoken serves attendance, not work. A person with nothing to add should be able to pass without it being remarked on.
Leave out demos and design reviews. Both are valuable and both are longer than fifteen minutes. They deserve their own slot, and putting them in the standup is how the standup grew to half an hour in the first place.
Leave out anything that exists to reassure a stakeholder. If a stakeholder needs visibility, give them the board and a weekly written summary. A board with kanban, Gantt, calendar and chat in one place makes that summary cheap to produce, which removes the main reason people defend the status meeting.
| Format | Who speaks | Fits when | The cost |
|---|---|---|---|
| Round robin by person | Everyone, in order | The team is four people or fewer and the work is independent | Grows linearly with headcount, and nobody hears the connections |
| Walk the board | Whoever owns each item | Work is on a shared board and items pass between people | Requires the board to be accurate before the meeting starts |
| Written, then a short call | Everyone writes, some talk | Hours overlap badly or the team is spread across time zones | Written updates go unread unless someone summarizes them |
The middle row is the default worth trying first, because it fixes the audience problem and the length problem at the same time. The condition attached to it is real though. Walking the board only works if the board is true, and the board is only true if updating it is faster than describing the update in a meeting. When updating a card costs three clicks, people do it. When it costs a login, a search and a form, they save it for the meeting, and the meeting grows back.
Written standups deserve more credit than they usually get. The cost of writing is paid by the person with the most context and the benefit is spread across everyone who reads asynchronously. The failure mode is that written updates pile up unread. The fix is to assign one person each week to read them and raise only the items that need a decision.
A blocker recorded in a meeting and nowhere else is not recorded. This is where most standups leak value, and it is the cheapest thing on this list to fix.
A usable blocker has four parts. What is stuck, what it is waiting on, who is going to unstick it, and by when. Three of those are usually stated in the meeting. The fourth, the date, is the one that gets dropped, and without it the blocker reappears tomorrow in the same words.
Where the blocker lives matters as much as whether it is written. A blocker inside a chat message from Tuesday is functionally invisible by Thursday. A blocker attached to the card it is blocking travels with the work, shows up in the next standup automatically, and does not need anyone to remember it. That is the practical case for keeping conversation and cards in the same tool rather than two, and it is the same argument that shows up when teams compare a chat tool with a board tool.
Escalation needs a named route as well. If a blocker is owned by someone outside the team, the standup cannot resolve it, and pretending otherwise wastes a week. Decide in advance who carries an external blocker outward and how long it sits before it is raised. Two days is a common threshold and any number works as long as it is agreed rather than improvised.
Distributed teams break the standup in two specific ways. Hours do not overlap, and nobody can read the room.
For hours, write first. Each person posts a short update in the same place at the end of their day, and the shared call happens during whatever overlap exists, using the written updates as the input. The call then covers only disagreements and decisions, which usually takes five minutes rather than fifteen.
For the missing room, be explicit about things that are normally implied. Say who is picking up what. Say when something is being dropped. Silence reads as agreement on a call and as absence in a thread, so the facilitator has to ask directly rather than waiting for objections.
Two mechanical details matter more than they should. Keep the update in one place, not in a thread that moves, so that a person joining after a holiday can read four days in four minutes. And keep a written record of decisions in the same tool as the work, because a decision recorded in a meeting tool is separated from the task it changes within a day.
Pick one change and run it for two weeks: walk the board from right to left instead of going person by person, and end every stuck item with a name and a date. Keep the time box and let the meeting finish early when it can.
If blockers keep getting lost between chat and cards, the standup is not the problem and a second tool is not the answer. Putting the board, the schedule and the conversation in one place is what makes the fifteen minutes hold, and Pinateca is free for up to five people and ten boards if you want to test that without a procurement conversation.
Fifteen minutes is the standard time box and it is enough for a team of five to ten people if the meeting walks the work rather than the people. If it consistently runs longer, the usual causes are problem solving inside the meeting and person by person updates. Both are fixable without adding time.
No, and requiring it is one of the reasons standups get long. If the meeting walks the items in progress, the people who own those items speak and the rest listen. Someone with nothing to add should be able to pass without it being treated as a problem.
Put it on a short list during the meeting and handle it immediately afterward with only the people it concerns. Naming that list out loud gives the facilitator a polite way to stop a conversation rather than letting it consume the rest of the time box. Most days that list has one or two items on it.
It depends on overlap. When working hours barely overlap, written updates plus a short call for disagreements usually work better than forcing everyone onto one call. When the team shares most of a working day, a live fifteen minute walk of the board tends to surface connections that written updates miss.
Only if they are doing the work being discussed. The presence of an audience turns replanning into reporting, because people start addressing the senior person in the room. If a manager needs visibility, a shared board and a weekly written summary give them more than a daily meeting does.