In an era where customer success and sentiment are paramount, reducing time to market is crucial for generating revenue and capturing market share. At the same time, in the age of VUCA (Volatile, Uncertain, Complex, Ambiguous), adopting and implementing Agile methodologies has become the key to success. To thrive, our project/program management or operations must embrace Agile principles and values, which focus on continuous inspection, adaptation, frequent software releases, psychological safety for team members, closer collaboration with the customer, and proactive risk and issue identification. Additionally, Agile encourages detailed planning for the near future.
To deliver frequently and at short intervals, accept change during the project, course-correct early, and build incrementally, it is essential for the team members or development team to meet daily. These meetings help plan each day, validate actual progress against the plan, course-correct swiftly, and eliminate blockers immediately. This meeting is none other than the Daily Scrum Meeting.
In this blog, I’ll explore the purpose of the Daily Scrum meeting, provide valuable pointers, and offer a format and agenda for conducting effective daily Scrum sessions. All of these insights are based purely on our consulting experience.
What is a Daily Scrum Meeting?
Let me first clarify these three words: Daily, Scrum, Meeting. As the terms suggest, these are daily recurring meetings conducted by the Scrum Team, for the Scrum Team, within the Scrum framework. During this meeting, developers and QA come together to revisit the plan created during Sprint Planning, assess the progress toward the Sprint Goal, check if the timelines are on track, discuss any deviations (if any), and identify and address any issues or blockers.
Now, you might wonder if this is similar to a Daily Standup Meeting. Well, the Daily Standup originated from the Daily Scrum. I often recommend using a Daily Standup meeting, regardless of the framework. The intent is to gather as a team to review progress against the plan and make quicker, earlier course corrections. Whether it’s a Daily Scrum or a Daily Standup, the purpose remains the same: to create planned opportunities for inspection and adaptation.
Objectives and Importance of Daily Scrum Meetings
The Daily Scrum meeting is held every day at the same time and place. In a virtual or distributed environment, the Daily Scrum is booked as a recurring event, typically lasting around 15 minutes, and is conducted by the Scrum team. The daily scrum meeting purpose is to foster openness. Lets see a few benefits below.
The daily scrum meeting brings visibility. In other words, the Daily Scrum can serve as both a communication tool and an early warning indicator, as the team meets daily to discuss progress, identify where co-developers need help, and spot risks and issues at an early stage.
The Daily Scrum also provides an opportunity for the Scrum team to track their progress. Team members move tasks in their chosen Agile tool to reflect their current status, showcasing completed work items.
It’s highly rewarding for the team when they can see their tasks move from “To Do” to “In Progress” and finally to “Done.” This tangible progress reinforces the team’s momentum.
Additionally, the Daily Scrum meeting provides confidence and reassurance to the Product Owner, as the team discusses the progress made toward the sprint goal.
Another important benefit of the Daily Scrum meeting is that it allows developers and testers to understand when code will be integrated or ready for testing.
Beyond tracking progress and identifying blockers, the Daily Scrum also promotes knowledge sharing among team members.
This daily sync-up among team members strengthens the bond and fosters better collaboration within the team.
Daily Scrum Meeting Agenda
After planning the sprint on the first day of the iteration, the Scrum team begins their work. The Daily Scrum meeting agenda is to understand the progress made toward the committed sprint goal, make faster course corrections and identify blockers.
Participants of a Daily Scrum Meeting
Mandatory participants are the Scrum team, consisting of developers and testers. If designers are delivering designs that contribute to the sprint goal, they should also attend. For mature teams, the Scrum Master’s participation is optional. If the team needs the Scrum Master, they can invite them and seek help during the meeting. The Product Owner is also optional, as long as the Scrum team has functional clarity. If the Scrum team is dependent on another team, members of the dependent team can participate in the Daily Scrum meeting as well.
Daily Scrum Meeting Format
The Daily Scrum meeting is a short and focused meeting that takes place at the same time and place every day. One of the Scrum team members (every member takes turns to share the team board), or the Scrum Master, opens the team board in Jira or any other ALM tool. Each team member provides updates on their status, blockers, etc. The team member’s status being talked about must reflect on the ticket being worked upon on the Jira/ALM tool’s team board. Once everyone has shared their updates, the meeting ends.
The Daily scrum meeting format or agenda of the Daily Scrum should be called out at the beginning of every meeting until the Scrum team becomes accustomed to it. This repetition helps the team stay focused and ensures the meeting becomes a habitual, efficient part of their routine.
Daily Scrum Meeting Three Questions
During the Daily Scrum meeting, which is typically timeboxed to 15 minutes, each team member answers the following three questions which reflects the daily scrum meeting agenda:
What did you work on since yesterday/our last meeting?
What do you plan to accomplish today?
Are there any blockers or impediments preventing you from meeting your sprint goal?
Skip to content 
