Meeting canvases · Team routines

Daily standup meeting template, and a board that fills in as you talk

A daily standup, or stand-up, is a short meeting at the same time each working day where a team checks progress, plans the day and raises what is blocking it; in Scrum it is the fifteen-minute Daily Scrum. It works when people talk to each other about the work, not report to a manager, and every blocker leaves with someone to clear it.

Troopa builds the stand-up board for you on Teams, Zoom or Google Meet: a row for each person with what they finished, what they will do next and what blocks them, filled in as you go round. When the meeting is called a stand-up, Troopa offers the board before anyone speaks.

The Scrum Guide (2020), by Ken Schwaber and Jeff Sutherland →

14 days free, no card. Then $15 per seat, per month. Cancel any time. Last checked against the product on 21 October 2026.

Why stand-ups drift

  • It turns into a status report for the manager, and people stop listening to each other.
  • Fifteen minutes becomes forty, because every blocker gets solved on the spot while everyone else waits.
  • The same blocker is raised every morning for a week, and nobody has said they will clear it.
  • Updates are “still working on the same thing”, so nobody learns anything they did not know.
  • People on a bad line, or who missed a word, lose the thread, and the people in the room never notice.
  • Somebody takes notes nobody reads, or nobody takes any and yesterday’s blockers are forgotten.

How to run a daily standup with Troopa

  1. Step 1: Say yes as it starts

    When the meeting is called a stand-up, Troopa offers: “Keep a stand-up board as you go round?” Or say “Hi Troopa, let’s do the stand-up board”.

  2. Step 2: Go round

    Each person’s update goes in their own row, whoever gives it: done since last time, doing next, and blockers.

  3. Step 3: See every blocker at once

    Blockers sit in a column of their own, so the room sees them all together and can agree who helps whom after the call.

  4. Step 4: Present it while you talk

    Shared on screen, the board lets everyone follow the round, including whoever is on a poor line or missed a word.

  5. Step 5: Keep it for tomorrow

    Download it as Markdown or CSV, or leave it with the meeting’s notes, where tomorrow’s stand-up can check what happened to today’s blockers.

A worked example: a payments squad’s daily

A payments squad meets on Microsoft Teams at half past nine. The meeting is called “Payments squad daily”, so Troopa offers the board as it starts, and Ines presses Open the stand-up board.

  1. Troopa, on your screen“Keep a stand-up board as you go round?”
  2. Kwame“Yesterday I finished the refund webhook. Today it’s the retry queue. Nothing blocking me.”
  3. Mei“I merged the fee calculator. Next is the statement export, but I’m blocked: we still have no sandbox keys from the bank.”
  4. Ines“I’ll chase the bank straight after this. I finished the release notes, and today it’s the audit fixes.”
  5. Tom“Still on the dispute form. I’m waiting on legal for the wording.”
Stand-up board: the board from the exampleA stand-up board with a row each for Kwame, Mei, Ines and Tom. Done since last time: refund webhook; fee calculator merged; release notes. Doing next: retry queue; statement export; audit fixes and chasing the bank for keys; dispute form. Blockers: Mei has no sandbox keys from the bank; Tom is waiting on legal for wording.Stand-up boardPayments squad dailyDownloadPresentDone sincelast timeDoing nextBlockersKwameRefund webhookRetry queueMeiFee calculator mergedStatement exportNo sandbox keys fromthe bankInesRelease notesAudit fixesChase the bank forkeysTomDispute formWaiting on legal forwording10 updates from 4 people · 2 blockers
The board after one round, in under ten minutes: a row for each person, Tom’s outlined as the last to speak, and two blockers in their own column, one of which Ines took away to chase as soon as the stand-up ended.

The same meeting under other names

  • Public sector service teams

    A hybrid service team walks its virtual team wall for fifteen minutes each morning on Teams, with the format chosen so the people working remotely take part as fully as the people in the room.

  • Healthcare operations

    A daily operations huddle across several sites: staffing gaps, rooms and equipment ready or not, supplies, and IT problems, ten minutes or less. Operational only, with no patient details on the board.

  • Manufacturing

    The daily tier meeting that joins several lines or sites on a call: safety, quality, delivery and the problems that need an owner today, the way lean teams run huddles at their tracking boards.

  • Construction

    The morning coordination call between the site and the design team working remotely: what is done, what is next today, what is in the way, and the safety briefing to close.

  • IT operations and support

    A service desk’s morning check: what was closed overnight, what is being worked today, and which tickets are stuck waiting on another team, so the stuck ones get a name.

A daily standup meeting template, two ways

Go person by person when the team is small, or walk the board when the work matters more than who is talking. Either way, keep it to fifteen minutes and take any problem-solving to straight after.

Stand-up: [team], [date]    Goal this sprint or week: [one line]

Person by person
Name    | Done since last time | Doing next | Blocked, and who can help
[name]  | [an outcome]         | [one thing]| [the blocker] · [who]

Or walk the board, right to left
1. What is blocked, and who will clear it?
2. What is urgent?
3. What has not moved since yesterday, and why?
4. Everything else, in order of priority.

Blockers: [blocker] · [owner] · [next step] · [check again on]
After the stand-up: [topic] · [who needs to stay]

How to keep a stand-up short and useful

  • Talk to the team, not to the person leading it: the stand-up is for coordinating, not reporting.
  • Say what you finished, not what you were busy with.
  • When a problem comes up, name who will solve it and do it straight after, with only the people it needs.
  • Give every blocker an owner, and check it first thing tomorrow.
  • Rotate who runs it, so it does not become one person’s meeting.
  • If time zones make a live stand-up unfair, write the updates instead, and meet live only to clear blockers.
Jason Yip, It’s not just standing up: patterns for daily standup meetings (martinfowler.com) →

Questions about daily standups

What are the three daily standup questions?

What did I do yesterday, what will I do today, and what is blocking me. The Scrum Guide dropped them in 2020 and leaves the format to the team, as long as the meeting looks at progress toward the goal and ends with a plan for the day, but many teams still find the three questions a good default.Scrum Guide revision history →

How long should a daily standup be?

Fifteen minutes or less. The Daily Scrum is set at fifteen minutes, and stand-ups and huddles outside software usually run ten to fifteen. Anything longer usually means problems are being solved in the meeting rather than after it.The Scrum Guide (2020), by Ken Schwaber and Jeff Sutherland →

What is the difference between a standup and a Daily Scrum?

The Daily Scrum is the Scrum framework’s name for its daily meeting, fifteen minutes for the developers, focused on the sprint goal. A stand-up is the wider name, used by teams that follow Scrum and teams that do not; the name comes from standing up to keep the meeting short.

Should a manager attend the daily standup?

They can listen, but the meeting belongs to the team. When people start speaking to the manager rather than to each other, the stand-up has become a status report, and the cure is usually for the manager to stay quiet or to get their update elsewhere.Agile Alliance glossary, Daily meeting →

Should you take notes at a standup?

Good standup notes are the board, the blockers with their owners and anything parked for after, rather than minutes. That is enough for the next day’s stand-up to check whether yesterday’s blockers were cleared, which is the part teams most often forget.

Is an async standup better than a live one?

It depends on the team. Written updates suit people spread across time zones or who need long stretches of focus. A live stand-up is better when the work is tightly linked, the team is new, or a blocker needs clearing today.

Sources

  1. The Scrum Guide (2020), by Ken Schwaber and Jeff Sutherland
  2. Scrum Guide revision history
  3. Agile Alliance glossary, Daily meeting
  4. Jason Yip, It’s not just standing up: patterns for daily standup meetings (martinfowler.com)

Read on 15 October 2026, by the people who make Troopa.

Try it in your next meeting

Install Troopa on your Mac, Windows PC or Ubuntu computer, join your call on Teams, Zoom or Google Meet as you always do, and ask: “Hi Troopa, let’s do stand-up board.”

14 days free, no card. Then $15 per seat, per month. Cancel any time.