/

Templates / Projects and agile

Daily standup

Daily standup meeting template

A daily standup is a 15-minute check-in where the team looks at progress toward the sprint or week goal, plans the next day of work and raises blockers. "Yesterday, today, blockers" is one common way to run it, not the definition: in Scrum, the Developers choose the structure. Standup notes only need three things written down: the blockers with the person who will help clear them, the topics moved to the parking lot, and any action items, because the rest already lives on the team's board.

Best forSoftware, operations and project teams of 3 to 10 working toward a shared goal

Meeting length15 minutes, same time every day

SectionsSprint or week goal, optional updates (yesterday, today), blockers, parking lot, action items

FormatsGoogle Docs, Word, Notion, Markdown

Word Markdown

Daily standup: [team].docx

Daily standup: [team]

Date Team Sprint or week goal AbsentName, and whether they posted an update in chat

Updates (optional)

Name	Yesterday (finished)	Today	Blockers
Fill in only if the board doesn't already show it			None, or what is stuck

Blockers

Blocker	Affects	Who will help	First raised
			Date, so old blockers stand out

Parking lot (after standup)

Topic	Who stays

Action items

Item	Owner	Due

Word MarkdownPastes into Google Docs, Word or Notion with headings and tables intact.

Word Markdown

Daily standup agenda.docx

Daily standup agenda

Time15 min, dailyFacilitatorRotates weeklyBoardOpen on screen

Item	Owner	Time	What we need to leave with
Goal reminder	Facilitator	1 min	Everyone knows what this sprint or week is for
Progress toward the goal (one format: yesterday, today, blockers; or walk the board)	Each person	10 min	About a minute each, about the goal, not a list of tasks
Blockers	Facilitator	2 min	A named helper for each blocker
Parking lot	Facilitator	2 min	Who stays behind for which topic, everyone else leaves

Word MarkdownPastes into Google Docs, Word or Notion with headings and tables intact.

Brightwater Apps payments team standup, Sprint 21, day 4

Filled-in example

Brightwater Apps payments team standup, Sprint 21, day 4

DateThursday, October 22, 2026, 9:30 to 9:44 amTeamPayments: Nadia Romero (lead), Felix Han, Grace Mbeki, Arjun Desai, Lucy TranSprint or week goalCustomers can get a partial refund from the order page without contacting supportAbsentLucy Tran (appointment), posted her update in the team channel

Updates (optional)

Name	Yesterday (finished)	Today	Blockers
Felix	Partial refund endpoint merged	Tests for refunds larger than the original charge	None
Grace	Refund button design approved by Nadia	Refund form on the order page	Needs the endpoint's error codes from Felix
Arjun	Nothing finished. Still setting up the payment provider sandbox (day 3).	Same	Sandbox keys expired, needs an admin to reissue them
Lucy (in chat)	Support reply template for partial refunds drafted	Review it with the support lead	None
Nadia	Reviewed refund button design	Confirm refund limits with finance	None

Blockers

Blocker	Affects	Who will help	First raised
Payment provider sandbox keys expired	Arjun, all refund testing	Nadia (has admin access)	Oct 20
Refund endpoint error codes not written down	Grace, refund form	Felix	Oct 22

Parking lot (after standup)

Topic	Who stays
Do refunds over $500 need a manager approval step? Finance hasn't answered.	Nadia, Felix
Checkout test failing on main again. Not decided who looks at it, raise at Friday's backlog refinement.	Felix, Arjun

Action items

Item	Owner	Due
Reissue sandbox keys for Arjun	Nadia	Oct 22, before noon
Post refund error codes in the team channel	Felix	Oct 22
Get a yes or no from finance on approval for refunds over $500	Nadia	Oct 23

Brightwater Apps and everyone on its payments team are a fictional sample.

Best forSoftware, operations and project teams of 3 to 10 working toward a shared goal

Meeting length15 minutes, same time every day

SectionsSprint or week goal, optional updates (yesterday, today), blockers, parking lot, action items

FormatsGoogle Docs, Word, Notion, Markdown

What to write in each section

Goal

Read the sprint or week goal in one line at the start (for a sprint, the goal set at sprint planning). Updates should be about progress toward it, not a list of everything someone touched.

Yesterday (finished)

What got finished, not what got worked on. If it's already marked done on the board, a few words is enough.

"Refund endpoint merged", not "worked on refunds".

Today

What the person expects to finish or move forward today. If it's the same answer for the third day running, treat it as a blocker.

Blockers

Anything stopping progress, with the person who will help clear it and the day it was first raised. Write it down and move on. The fix happens after standup.

Parking lot

Topics that need more than 30 seconds, and who needs to stay behind for each. This list is what keeps standup at 15 minutes.

When to use this template

Your standup runs 30 minutes because problems get solved in the middle of it.
The same blocker gets mentioned on Monday and is still being mentioned on Thursday.
You run a morning meeting or shift huddle for a non-software team and want a short format that's the same every day.

Questions people ask

Do we have to use the three standup questions?: No. Yesterday, today and blockers is a common habit, but the current Scrum Guide says the Developers can pick whatever structure and techniques they want, as long as the Daily Scrum inspects progress toward the Sprint Goal and plans the next day. Many teams walk the board instead, from the right-hand column to the left, and talk about each item in progress. Use whichever gets blockers out faster.
How do you run a weekly standup?: A weekly standup suits teams that don't share daily work, like a sales team or people spread across projects. Use the same table with last week, this week and blockers, allow two minutes per person, and keep it under 30 minutes.
Should someone take notes at standup?: Only blockers, parking lot topics and action items. Writing down every update copies the board and nobody reads it. The rule is the same as for writing meeting minutes: record outcomes, not every word. The facilitator can type the blockers straight into the template while people talk.

Sources

The Scrum Guide (November 2020)Defines the Scrum events and their maximum timeboxes, and the Daily Scrum as a 15-minute event for the Developers, who choose its structure.

Related templates

Scrum meeting template for sprint planningScrum teams, typically 10 or fewer people including the product owner and scrum masterAgenda · Template · Example

Backlog refinement meeting agendaScrum and agile teams, once or twice per sprint, product owner plus developersAgenda · Template · Example

Team meeting agenda and notes templateTeams of 3 to 12 people who work together every weekAgenda · Template · Example