Varaa demo Kokeile Speak AI:ta ilmaiseksi Kirjaudu sisään

Scrum Meeting Minutes Template for Daily Scrum and Sprint Events

Use this template to record a scrum event in a form the whole team can scan in a minute. It captures the sprint goal, progress, blockers and the decisions that change the plan.

Varaa demoKokeile Speak AI:ta ilmaiseksi

Used by 300,000+ individuals and teams. Free trial, no credit card required.

Scrum meeting minutes: the template

Eight sections cover a daily scrum and can be stretched for planning, review or a retrospective. The examples follow a two-week sprint, day 6.

Scrum meeting minutes

Fill in during or right after the meeting

  • Team: [Team name]
  • Event: [Daily scrum, planning, review or retrospective]
  • Sprint: [Sprint number and dates]
  • Date and time: [Date, start and end time]
  • Scrum Master: [Name]
  • Product Owner: [Name]
  • Present: [Developers and others]
  • Absent: [Names and cover]

Sprint goal and progress

Repeat the sprint goal and say whether the team is on track, with the burndown or the count of done items.

ExampleGoal: customers can export reports as CSV. Day 6 of 10. 9 of 16 points done, on track.

Done since the last scrum

Items moved to done, with the person and the ticket reference. Note anything that met the definition of done.

ExampleExport endpoint merged (Ana, TEAM-212). Date filter tested on staging (Joe, TEAM-215).

Planned for the next 24 hours

What each developer will pick up next, one line each.

ExampleAna: pagination on exports. Joe: error handling for empty reports. Mina: write acceptance tests.

Blockers and impediments

Anything stopping work, with who can clear it and by when. The Scrum Master owns the follow-up.

ExampleStaging database is out of sync, blocking TEAM-218. Scrum Master asks platform team by noon.

Scope and backlog changes

Items added, removed or re-estimated, and who agreed. Note any effect on the sprint goal.

ExampleProduct Owner moved XLSX export to the next sprint. Goal unchanged.

Decisions made

Each decision on its own line, with the decision maker. Keep the reason in a few words.

ExampleUse streaming for exports over 50,000 rows (team, to avoid timeouts).

Parked topics

Discussion that ran past the time box and who takes it offline, with a meeting time.

ExampleTest data strategy: Joe and Mina meet at 2 pm after the scrum.

Next event and notes distribution

Date of the next scrum event and where the minutes are stored.

ExampleNext daily scrum 9:30 tomorrow. Minutes on the team board under Sprint 14.

Toimintakohteet

Task Omistaja Due
Resync the staging database so TEAM-218 can start Scrum Master Today, noon
Add streaming export to the sprint board as a sub-task Ana Today
Update the sprint board to show XLSX export in the backlog Product Owner Tomorrow
Copy as textDownload .txtPrint or save as PDF

Copy-ready minutes text

Paste this into Google Docs, Word, Notion or an email. Replace anything in [brackets].

Copy the text
SCRUM MEETING MINUTES

Team: [Team name]
Event: [Daily scrum, planning, review or retrospective]
Sprint: [Sprint number and dates]
Date and time: [Date, start and end time]
Scrum Master: [Name]
Product Owner: [Name]
Present: [Developers and others]
Absent: [Names and cover]

SPRINT GOAL AND PROGRESS
[Repeat the sprint goal and say whether the team is on track, with the burndown or the count of done items.]

DONE SINCE THE LAST SCRUM
[Items moved to done, with the person and the ticket reference. Note anything that met the definition of done.]

PLANNED FOR THE NEXT 24 HOURS
[What each developer will pick up next, one line each.]

BLOCKERS AND IMPEDIMENTS
[Anything stopping work, with who can clear it and by when. The Scrum Master owns the follow-up.]

SCOPE AND BACKLOG CHANGES
[Items added, removed or re-estimated, and who agreed. Note any effect on the sprint goal.]

DECISIONS MADE
[Each decision on its own line, with the decision maker. Keep the reason in a few words.]

PARKED TOPICS
[Discussion that ran past the time box and who takes it offline, with a meeting time.]

NEXT EVENT AND NOTES DISTRIBUTION
[Date of the next scrum event and where the minutes are stored.]

ACTION ITEMS
Task | Owner | Due
[Task] | [Name] | [Date]

Next meeting: [Date, time]
Minutes prepared by: [Name]

How to run this meeting

  1. Keep minutes short enough to read

    A 15-minute daily scrum needs a half-page record at most. Write down blockers, decisions and changes to scope, and leave out each person's full update because the board already shows it.

  2. Name an owner for every blocker

    A blocker without a name stays a blocker. Record who can remove it and by what time, then check it at the start of the next scrum.

  3. Use longer minutes for planning, review and retro

    For sprint planning, add the chosen sprint goal and the forecast. For review, record stakeholder feedback and backlog changes. For retro, record two or three experiments with owners.

  4. Post the minutes where the team already looks

    Put them in the sprint board, ticket comment or team channel within an hour. Minutes in a separate document nobody opens are the same as no minutes.

Get scrum minutes from the call, not from memory

Daily scrums are short and fast, which makes them hard to note by hand. Speak AI joins your Zoom, Google Meet or Microsoft Teams stand-up, or accepts an uploaded recording, and writes up the blockers and decisions.

  • Record the daily scrum, planning, review or retro on your usual video tool, or upload the file.
  • Get a transcript with each developer labelled, so updates and blockers are easy to find.
  • Get an automatic summary of progress, blockers and decisions to paste under each section.
  • Get action items with owners, such as who clears which blocker, ready for your sprint board.

See how the Tekoälykokousavustaja ja Tekoälyinen muistiinpanojen tekijä work, or start with a free account.

Varaa demoKokeile Speak AI:ta ilmaiseksi

Usein kysytyt kysymykset

What is the main purpose of minutes of a scrum meeting?

Scrum minutes record what changed and what is blocked, not each person's update. They keep a trail of decisions, scope changes and impediments so absent team members, stakeholders and the Scrum Master can see what happened without asking.

Which is the time box for a daily scrum meeting?

The daily scrum is time-boxed to 15 minutes regardless of team size. Keep it at the same time and place each day. Anything that needs longer discussion is parked and taken offline by the people involved.

How do scrum meetings work?

A scrum team runs five events in a sprint: the sprint itself, sprint planning, daily scrum, sprint review and sprint retrospective. Developers, the Product Owner and the Scrum Master each have set roles, and each event has a time box and purpose.

What is the 3 5 3 rule in Scrum?

It is a shorthand for three roles, five events and three artifacts. The roles are Product Owner, Scrum Master and Developers. The events are sprint, planning, daily scrum, review and retrospective. The artifacts are product backlog, sprint backlog and increment.

Do you need minutes for every daily scrum?

Not always. Many teams write minutes only when a blocker, scope change or decision comes up, and rely on the board for the rest. Always keep minutes for planning, review and retrospective, where decisions and feedback matter.

Related templates and tools

Daily Check In Meeting Agenda TemplateDebrief Meeting Minutes TemplateBrainstorming Session Minutes TemplateAll meeting templatesAI Meeting AssistantAI Notetaker

Skip the typing and get scrum notes from the call

Book a demo to see Speak AI turn a recorded stand-up or sprint event into a summary, blockers and action items, or try it free.

Varaa demoKokeile Speak AI:ta ilmaiseksi