Template
Stand‑Up Meeting Agenda & Minutes Template
Run concise daily scrums with this Stand‑Up Meeting Agenda & Minutes template in Noota.
0
sections
Stand‑Up Meeting Agenda & Minutes Template
Date
DD / MM / YYYY
·
Attendees
Names
Meeting Purpose & Timebox
Clarify that this is a 15‑minute daily sync focused on progress and impediments.
Attendance & Roles
List attendees and their roles (Scrum Master, Developers, QA, PO).
Yesterday’s Completed Work
Each team member states what they completed since the last stand‑up.
Today’s Planned Work
Each team member shares what they plan to accomplish before the next stand‑up.
Blockers & Impediments
Surface blockers impeding progress; assign owners to resolve them.
Sprint Goal & Burndown Review
Quick glance at sprint goal alignment and burndown chart trend.
Dependencies & Coordination
Highlight tasks requiring collaboration with other teams or external stakeholders.
Action Items & Ownership
- Record each action item with an owner and due date (ideally today).
Impediment Escalation Plan
If blockers cannot be solved immediately, outline escalation steps.
Parking Lot Topics
Capture off‑topic discussions for follow‑up outside the stand‑up.
Meeting Close & Next Stand‑Up
Summarise key takeaways, confirm next stand‑up time, and adjourn.
Built into Noota
Stop filling templates by hand. Noota fills them from the conversation.
Use one of these, or build your own report template in Noota, as many as you like.
Meet, Teams, Zoom, Webex, a phone call or in person, with a bot or without one.
A few minutes after the call, the report follows your template, section by section, ready to share or send to your tools.
Why Daily Stand‑Ups?
Daily stand‑ups (or daily scrums) give cross‑functional teams a lightweight mechanism to synchroniseprogress, identify blockers early, and reinforce the sprint goal. By limiting updates to a quickthree‑question format, teams minimise context switching and maintain momentum.
Preparation Checklist
- Update task status on your board before the meeting (Jira, Trello, Linear, etc.).
- Review open pull requests or merge requests.
- Have your blocker list ready—dependencies, approvals, environment issues.
- Open the sprint burndown chart for a quick reference.
