Skip to content
ruam.ai

Daily standup template: questions, agenda and an async version

A copyable daily standup template: better questions, a 15-minute live agenda, a written async version, and how to keep it from feeling like surveillance.

Indrayudh Sen

, 7 min read

A daily standup is a short, regular check-in where each person says what they finished, what they are doing next, and what is in their way. The best version for most remote and hybrid teams is a 15-minute live call, or a written update posted at a set time, with questions that surface blockers instead of status. Below are the questions, a live agenda and an async template you can copy today, plus when to pick which.

What a daily standup is for

The standup comes from Scrum, and the Scrum Guide is clear about its job. The Daily Scrum exists “to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary.” It is a 15-minute event for the people doing the work, held at the same time and place each working day, and it should produce a plan for the next day of work (The Scrum Guide, Daily Scrum).

Two things in that definition are easy to lose. The meeting is for the people doing the work. A manager collecting status is not its job. And the Guide lets the team choose its own structure, as long as the meeting stays focused on progress toward the goal.

You do not need to run Scrum to use a standup. The useful part is a predictable moment each day where people line up their work and raise problems early.

The classic three questions, and better wording

Most teams know these:

  1. What did you do yesterday?
  2. What will you do today?
  3. Is anything blocking you?

They work, but they drift. “What did you do yesterday” invites a list of busyness. “Is anything blocking you” gets a reflexive “no.” Here is wording that gets more honest answers.

Classic questionBetter versionWhy it helps
What did you do yesterday?What got finished, and what moved forward?Separates done from in progress.
What will you do today?What is the one thing that matters most today?Forces a priority, not a list.
Is anything blocking you?What is slowing you down, even a little?Lower bar than “blocked,” so small problems come out early.
(not asked)What changed that affects someone else?Catches handoffs, new decisions and shifted dates.
(not asked)Who do you need something from?Turns a vague worry into a named request.

The fourth question is the one most teams are missing. Many surprises on a team are not blockers. They are changes: a customer asked for something different, a date moved, a decision was made in a thread someone else did not see. Asking about change out loud makes people notice it.

You do not need all five every day. Pick three.

A copyable 15-minute live agenda

Use this for a live standup of up to about eight people. Bigger groups should split into smaller standups by project.

Daily standup, 15 minutes, same time every working day

0:00  Start on time. One person facilitates (rotate weekly).
0:01  Go around the room, about 90 seconds each:
        - What got finished or moved forward
        - The one thing that matters most today
        - What is slowing you down, and who you need
0:11  Changes that affect others (anyone, 2 minutes max)
0:13  Parking lot: list topics that need a longer talk, with names
0:14  Read back the follow-ups: who, what, by when
0:15  End. The people in each parking-lot item stay; everyone else leaves.

A few rules that keep it at 15 minutes:

  • Talk to the team, not the manager. If everyone reports upward, it turns into a status meeting. Ask people to look at the group, or to address whoever they need something from.
  • Park the long talks. The standup finds problems. It does not solve them. Anything over 30 seconds of discussion goes on the parking lot.
  • Same time, same place. The Scrum Guide says to do this to reduce complexity, and it is also what makes the habit stick.

A copyable async written template

For teams spread across time zones, or teams that simply find a daily call a poor use of attention, a written update does the same job. Post it in a team channel or a shared doc at a set time, such as the first hour of each person’s day.

Daily update, [name], [date]

Done:
- [What got finished or moved forward since the last update]

Next:
- [The one thing that matters most today]
- [Anything else you expect to start]

Blocked or slowing down:
- [What is in the way, and who you need. Write "nothing" if nothing.]

Changed, affects others:
- [Any decision, date, scope or priority that changed and who it touches]

Tips that make it work:

  • Keep it short. If an update takes more than five minutes to write, it will not survive a bad week.
  • Name people in the blocked line. “Waiting on Sam for the API keys” gets answered. “Waiting on access” does not.
  • Read them. Nothing kills an async standup faster than writing updates nobody reads. If you manage the team, reply to at least the blocked lines the same day.

When async beats live, and when it does not

Neither format is better in general. It depends on the team.

SituationBetter choiceReason
Team spans many time zonesAsyncNo one has to join at midnight.
Work is mostly heads-downAsyncAvoids breaking focus for a call.
Team is new or just formedLivePeople learn each other’s work and voices.
Work changes by the hour (support, incidents, launches)LiveFast back-and-forth beats written replies.
Updates have become rote and nobody listensTry asyncA written record is skimmable, and the call time returns to the team.

A common middle path is async most days and a live call once or twice a week.

Keeping a standup from becoming surveillance

A standup is a trust exercise. It works when people feel the update is theirs, and it fails when they feel it is being used to judge them. A few habits protect that.

  • People write or say their own update. Do not fill it in for them from tool data, and do not edit it.
  • No scores. Do not rank people by how many items they list or how often they post. A long update is not a good one, and a short one is not a bad one.
  • Say what the standup is for. Tell the team in plain words: it is for catching blockers and lining up work, not for measuring anyone.
  • Keep private things private. If a tool collects a reflection or mood, the person should control who sees it.

Choosing a standup tool

Some tools ask each person for their update in chat and post the results, and you can also build a simple version with your chat app’s own workflows. Before you pick one, check three things: what it collects, who can see it, and whether you can export your data. Check the price on the vendor’s own page, because it changes.

Where Ruam fits

Ruam is automatic time tracking for teams and for people who work on their own. It is not a standup tool, and it does not replace your team’s daily check-in. It has one feature that sits next to a standup: the Daily Recap.

The Daily Recap is a two-minute end-of-day check-in. Your answers about the work, such as what you got done and what you’ll start with tomorrow, are shared with your team’s admins. You can also write a private note, which stays private. Mood and energy are optional, and you don’t have to answer any question.

On team plans, mood and energy show up only as an anonymous average, and only when five or more people contribute. And the recap is on by default, but a team can turn it off. It sits beside the Logbook, so a person can look at their hours and notes together over a week. Daily Recap and the Logbook are available on every plan, including Free. See pricing for the plans.

If your team lives in Slack, Ruam for Slack lets people run the web clock from Slack: /ruam start, /ruam break, /ruam back and /ruam end. On the extension or desktop app, /ruam status still shows the day. The replies are visible only to the person who typed the command. It does not post a standup for you, but it keeps the day’s start and finish in the place where the team already talks.

Ruam for Slack, with /ruam start and /ruam status commands in a Slack channel
Ruam for Slack: start and end the day with a command. Sample data.

What to do next

Pick one format this week. If your team is in one time zone, try the live agenda for two weeks, and keep the clock. If it is spread out, paste the async template into a team channel and ask for updates at a set time. After two weeks, ask the team what they would change.

If you want a quiet end-of-day habit that sits beside the standup, try the Daily Recap. It is on every plan, including Free. See pricing for what each plan adds.

Questions

What are the three daily standup questions?

The classic three are: what did you do yesterday, what will you do today, and is anything blocking you. Many teams reword them to ask what got finished, what matters most today, and what is slowing you down, and add a fourth about changes that affect others.

How long should a daily standup be?

Fifteen minutes. The Scrum Guide sets the Daily Scrum at 15 minutes, and the shorter limit is what keeps it from turning into a status meeting. If you need longer, use a parking lot and talk after.

Should a daily standup be async?

It can be, especially for teams in many time zones or with mostly heads-down work. Live works better for new teams and for work that changes by the hour. Many teams mix the two, with async updates most days and a live call once or twice a week.

Who should attend the daily standup?

The people doing the work. The Scrum Guide describes the Daily Scrum as an event for the Developers, and says the Product Owner or Scrum Master take part as Developers when they are working on items in the Sprint Backlog. A manager can listen in, but the meeting is not a report to them.

How do I stop a standup from feeling like surveillance?

Let people write or say their own update, never score them on it, never use it in reviews, and say plainly what the standup is for. Keep anything personal, such as a private note or mood, in the control of the person who wrote it.

Hours that count themselves.

By project, client and shift. No screenshots. Free forever for one person.

Try Ruam for free
Indrayudh Sen

Founder, Ruam

Indrayudh Sen, the founder of Ruam, has managed remote teams since 2020 and has run a cold email agency.

Newsletter

New articles by email.

One email when there's a new article. No spam, unsubscribe any time.

See our Privacy Policy.

More articles