Track progress toward your sprint goal
Use this daily scrum meeting template to help your scrum team provide updates on what they’re working on, share what they plan to work on, and raise any concerns or questions.
A Daily Scrum Meeting, also known as a daily stand-up, is a fundamental ceremony in Agile and Scrum methodologies. It's a short and focused meeting where the team gathers to synchronize activities, share progress, and identify any obstacles.
The goal is to foster collaboration, maintain transparency, and ensure everyone is aligned towards achieving the sprint goal.
Start the meeting by checking in with a quick icebreaker. Each team member should add their name on a sticky note. You can personalize each sticky note with a color to help visualize progress.
To keep the space tidy, write down the date, sprint number, and sprint goal at the top of the scrum board.
Then, the appointed scrum master asks each team member to answer the key questions:
Then, import the tasks and issues for the current sprint into the sprint backlog section.
Import all tasks and issues into the current sprint in the “sprint backlog” section. This is only temporary to show all the tasks and key action items at hand.
Tip: Change the color of the task to the color of the person responsible for the task.
Move tasks that are currently being worked on into the “In progress” column.
Move any tasks that have been finished into the “Complete” column.
Move any blocked tasks into the “Blocked” column.
If any blockers are identified, plan a meeting outside the scrum to follow up and discuss the issue with relevant team members.
The most common scrum meetings are:
Daily Scrum meetings (also referred to as daily stand-up meetings) are a common Agile ceremony where all team members can quickly share an update on progress and raise any blockers.
Each meeting is short and follows the same format. Use this template to track progress toward your sprint goal and resolve any issues that are inhibiting your team's work.
Generally, scrums are held and directed by a “scrum master” or a team member dedicated to scrum project management. A scrum master facilitates the order of conversation and keeps the cadence of updates.
Product managers should also be involved in scrum meetings to understand the scope of a project and completed tasks and to be proactive if any roadblocks or challenges appear.
Lastly, the scrum team involved in the sprint’s project must all be invited so that the whole team is kept up to date, which avoids any miscommunication or misunderstandings.
Daily scrums inform team members of progress on a specific project of a sprint. So this is an opportunity for your team to communicate progress on their tasks. Only tasks that are relevant to the team and the current sprint should be mentioned — avoid the mention of any individual tasks. This is because you want to keep the meeting brief and in motion.
The task should be specific and include the amount completed so everyone on the team understands the state of progress.
For example:
Team members should say what task they want to accomplish today. That way, team members understand the expected progress and can hold each other accountable for task achievement the next day.
For example:
Are there any roadblocks that are expected to delay progress? Is a team member still waiting for authorization or approval? Other helpful things to bring up are personal limitations, technology limitations, or team dependencies.
When roadblocks are brought to the table, teams can work together to find a solution or navigate procedures to avoid delays.
For example:
Mural is the only platform that offers both a shared workspace and training on the LUMA System™, a practical way to collaborate that anyone can learn and apply.