I’ve spent two decades building software, leading teams, and fine-tuning agile practices. In my experience, the Daily Scrum serves as a powerful checkpoint that helps each team member stay on track. It also enables open communication and quick issue resolution. Below, I’ll share my approach, which draws on years of running these short gatherings for software engineering teams in the FinTech arena. While it might sound simple, a Daily Scrum brings huge benefits if done well. Let’s walk through a clear method for organizing and running this daily event. Why the Daily Scrum Matters A Daily Scrum is a short, focused meeting. It typically lasts no more than 15 minutes. First, it offers a chance for teams to share their progress. Then, it provides an opportunity to identify and address any issues. Finally, it drives accountability, since everyone commits to small steps each day. The Daily Scrum promotes a regular feedback cycle. As a result, teams adapt quickly to changing priorities. This constant alignment helps maintain flow and prevents issues from staying hidden. An effective Daily Scrum can be a vital factor in delivering projects on time. Key Roles and Expectations Most Scrum teams include a Product Owner, a Scrum Master, and the Development Team. However, the Daily Scrum is usually led by the Development Team. The Scrum Master facilitates it, yet each team member has a voice. • Product Owner: May attend but should not dominate the discussion. • Scrum Master: Helps keep the meeting on track. In fact, they often coach the team to keep it concise. • Development Team: Shares updates, raises obstacles, and plans the day ahead. In addition, I like to keep the format predictable. We’re there to talk about three things: what happened since the last Daily Scrum, what the plan is until the next one, and any blockers stopping progress. Simple Steps to Run a Daily Scrum Keep It Short: First, aim for 15 minutes or less. For example, if you have a team of five, a quick round of updates should be enough to cover progress and obstacles. If the meeting drags on, it becomes less effective. Keep It Focused Secondly, structure the conversation around three basic points: What I did since yesterday
What I will do today
Any blockers that need help Similarly, avoid discussing long technical details. If more in-depth conversations are needed, schedule a follow-up. Align With the Sprint Goal Thirdly, link your Daily Scrum updates to your Sprint Goal. For instance, if the Sprint Goal is to finish a login feature, each person should mention how their tasks move that feature along. This helps the team see the bigger picture. Start and End on Time Also, starting on time shows respect for everyone’s schedule. Even though some people run late, the group can wait a few seconds. Then, begin promptly. On the other hand, do not stay past 15 minutes. If a topic is too large, the Scrum Master can invite relevant people to chat right after. Note Blockers Immediately Furthermore, encourage team members to raise blockers. A blocker could be a technical issue or a missing piece of information. Therefore, surfacing these issues early gives the team a chance to solve them before the next day’s Scrum. Consequently, the Sprint remains on track. Common Pitfalls and How to Avoid Them Derailing into Technical Deep-Dives Teams often shift from a quick update to a full-on design session. However, this is what we want to avoid in a Daily Scrum. In particular, save those deep discussions for a separate meeting. Thus, the daily event stays brisk and to the point. Lack of Preparation If team members come unprepared, the meeting drags. They might struggle to articulate the next steps or current blockers. Hence, it’s good to spend a minute before the meeting reviewing what you did and what you plan to do. Ignoring Blockers Despite the best intentions, some people hesitate to mention obstacles. This leads to delays. Therefore, the Scrum Master should remind the team to share blockers freely. As a result, you strengthen collaboration and prevent hidden surprises. My Personal Take I’ve run hundreds of Daily Scrums, and I’ve seen how they energize teams. Keep these meetings short, and keep them consistent. If you stick to the guidelines and timelines, you’ll see that these short daily check-ins really do work. If you’ve followed all of what I’ve said above and are still going beyond 15 minutes each day, it may be time to consider splitting your scrum team into multiple teams. In Conclusion A well-structured Daily Scrum gives clear communication and quick adaptation. It’s one of the most important scrum events. It keeps everyone informed about progress and obstacles. In short, this daily event can be a real game-changer for any agile team. I hope these tips help you create Daily Scrums that energize your crew. After all, the Daily Scrum stands as a cornerstone of agile workflows. By keeping it short, focused, and solution-oriented, you’ll see improvements in teamwork and product delivery. Ben has led multiple engineering teams over the course of a 20 year career in Software. He runs the blog Just Another Tech Lead and shares his insights on X and YouTube. When he’s not writing software, he’s building online calculators for fun! I’ve spent two decades building software, leading teams, and fine-tuning agile practices. In my experience, the Daily Scrum serves as a powerful checkpoint that helps each team member stay on track. It also enables open communication and quick issue resolution. Below, I’ll share my approach, which draws on years of running these short gatherings for software engineering teams in the FinTech arena. While it might sound simple, a Daily Scrum brings huge benefits if done well. Let’s walk through a clear method for organizing and running this daily event. Why the Daily Scrum Matters A Daily Scrum is a short, focused meeting. It typically lasts no more than 15 minutes. First, it offers a chance for teams to share their progress. Then, it provides an opportunity to identify and address any issues. Finally, it drives accountability, since everyone commits to small steps each day. The Daily Scrum promotes a regular feedback cycle. As a result, teams adapt quickly to changing priorities. This constant alignment helps maintain flow and prevents issues from staying hidden. An effective Daily Scrum can be a vital factor in delivering projects on time. Key Roles and Expectations Most Scrum teams include a Product Owner, a Scrum Master, and the Development Team. However, the Daily Scrum is usually led by the Development Team. The Scrum Master facilitates it, yet each team member has a voice. • Product Owner: May attend but should not dominate the discussion. • Scrum Master: Helps keep the meeting on track. In fact, they often coach the team to keep it concise. • Development Team: Shares updates, raises obstacles, and plans the day ahead. In addition, I like to keep the format predictable. We’re there to talk about three things: what happened since the last Daily Scrum, what the plan is until the next one, and any blockers stopping progress. Simple Steps to Run a Daily Scrum Keep It Short: First, aim for 15 minutes or less. For example, if you have a team of five, a quick round of updates should be enough to cover progress and obstacles. If the meeting drags on, it becomes less effective. Keep It Focused Secondly, structure the conversation around three basic points: What I did since yesterday What I will do today Any blockers that need help What I did since yesterday What I will do today Any blockers that need help Similarly, avoid discussing long technical details. If more in-depth conversations are needed, schedule a follow-up. Align With the Sprint Goal Thirdly, link your Daily Scrum updates to your Sprint Goal. For instance, if the Sprint Goal is to finish a login feature, each person should mention how their tasks move that feature along. This helps the team see the bigger picture. Start and End on Time Also, starting on time shows respect for everyone’s schedule. Even though some people run late, the group can wait a few seconds. Then, begin promptly. On the other hand, do not stay past 15 minutes. If a topic is too large, the Scrum Master can invite relevant people to chat right after. Note Blockers Immediately Furthermore, encourage team members to raise blockers. A blocker could be a technical issue or a missing piece of information. Therefore, surfacing these issues early gives the team a chance to solve them before the next day’s Scrum. Consequently, the Sprint remains on track. Common Pitfalls and How to Avoid Them Derailing into Technical Deep-Dives Teams often shift from a quick update to a full-on design session. However, this is what we want to avoid in a Daily Scrum. In particular, save those deep discussions for a separate meeting. Thus, the daily event stays brisk and to the point. Lack of Preparation If team members come unprepared, the meeting drags. They might struggle to articulate the next steps or current blockers. Hence, it’s good to spend a minute before the meeting reviewing what you did and what you plan to do. Ignoring Blockers Despite the best intentions, some people hesitate to mention obstacles. This leads to delays. Therefore, the Scrum Master should remind the team to share blockers freely. As a result, you strengthen collaboration and prevent hidden surprises. My Personal Take I’ve run hundreds of Daily Scrums, and I’ve seen how they energize teams. Keep these meetings short, and keep them consistent. If you stick to the guidelines and timelines, you’ll see that these short daily check-ins really do work. If you’ve followed all of what I’ve said above and are still going beyond 15 minutes each day, it may be time to consider splitting your scrum team into multiple teams . multiple teams In Conclusion A well-structured Daily Scrum gives clear communication and quick adaptation. It’s one of the most important scrum events . scrum events It keeps everyone informed about progress and obstacles. In short, this daily event can be a real game-changer for any agile team. I hope these tips help you create Daily Scrums that energize your crew. After all, the Daily Scrum stands as a cornerstone of agile workflows. By keeping it short, focused, and solution-oriented, you’ll see improvements in teamwork and product delivery. Ben has led multiple engineering teams over the course of a 20 year career in Software. He runs the blog Just Another Tech Lead and shares his insights on X and YouTube. When he’s not writing software, he’s building online calculators for fun! Ben has led multiple engineering teams over the course of a 20 year career in Software. He runs the blog Just Another Tech Lead and shares his insights on X and YouTube . When he’s not writing software, he’s building online calculators for fun! Just Another Tech Lead X YouTube online calculators

How to Get the Most Out of Your Sprint Reviews 

Agile: How to Write User Stories for Beginners

Mastering the Daily Scrum: A Practical Guide

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

ACE Your Software Engineering Interview With a Few Tips

The Noonification: The Future of DeFi - Emerging Evolution (11/3/2022)

10 Ways PMs Can Earn The Respect and Trust of Their Team

10 Terms Every Engineer Must Know

10 Subtle Superpowers of DevOps

ACE Your Software Engineering Interview With a Few Tips

The Noonification: The Future of DeFi - Emerging Evolution (11/3/2022)

10 Ways PMs Can Earn The Respect and Trust of Their Team

10 Terms Every Engineer Must Know

10 Subtle Superpowers of DevOps

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps