You are here: Home // Agile, Project Management Practice // The Importance of Daily Scrum

The Importance of Daily Scrum


Among the important, key Scrum practices will be the Everyday Scrum. It happens every day throughout each Sprint and the entire team participates.

Throughout this Daily Scrum everybody answers the following 3 questions:

1. What’s been accomplished since the last meeting?

2. What’s going to be carried out before the next meeting?

3. What obstacles are in the way?

Frequently people treat it as a typical status meeting and behave quite casually, which eventually could result in bad outcomes.

This isn’t a mere status update meeting where one person (Project Manager or team lead) collects details about who’s behind schedule. Rather, it’s a meeting in which each and every team member makes commitments to each other. This has the fantastic effect of helping all team members recognize the significance of these commitments and that their commitments are to every single other. The meeting just isn’t employed for problem-solving or problem resolution. Problems which are raised are discussed offline and usually dealt with by the relevant sub-group instantly right after the meeting. The Everyday Scrum should not take much more than 15 minutes.

It requires that team members are disciplined and don’t talk about impediments in detail throughout this meeting, only make sure others are informed. If required, they are able to discuss it with concerned team members separately.


One question may possibly arise here, why are only these three questions important and not discussion about what’s new?

High visibility of progress

It’s a place where each and every day, team members can see the progress of a project and simply see their contributions.

Boost estimation

By focusing on what a team member accomplished yesterday, the team member gains an exceptional understanding of flaws in his estimates. Gradually, it improves his estimation skill.


Team members choose their every day tasks and they are responsible for deciding the requirements for the Sprint. This helps them to comprehend their daily responsibilities. Thus, it aids team self-organization, and slowly team members gain the maturity required to commit to some thing appropriately or to deal with impediments efficiently.

Enhance the top quality

Daily communication helps to refactor the function too as improve the turnaround time necessary to get rid of impediments. It builds understanding and assists to rapidly apply and reuse the expertise.

Common Problems

Below are common problems that negatively impact the Daily Scrum:

Lack of a clear understanding of Scrum practices

If the team doesn’t have a clear understanding of Scrum practices, then the Every day Scrum takes the wrong shape and also takes much more time to total. Quite soon the team loses the positive effect of a Every day Scrum, it eventually becomes a status update meeting, and folks change its frequency from daily to weekly.

Old habit

It’s quite common hurdle. A great deal of individuals answer these questions like they had been supplying their status to the PM or Team Lead and not the ScrumMaster. Often team members only address the ScrumMaster even though supplying answers throughout the Daily Scrum, as if they are providing a typical status report. It has also been observed that team members typically present quite generic and high-level answers that cover much more than one person’s task.

Faced vital problem This occurs when a team member has faced some crucial problem that has a direct impact on his existing or upcoming tasks. Most of the time individuals start explaining the issue in great detail, which consumes a lot of time.

Communication problem

Often individuals aren’t able to concisely explain technical stuff. This is one more kind of communication difficulty.

Info about barriers shapes the discussion

It’s a common practice to engage in a discussion about barriers if someone is talking about it. That causes the Everyday Scrum to change into a discussion, and other people slowly become a component of it.

Begin requirement/design clarification/discussion

Men and women begin clarifying the requirement or start off discussing design throughout the Daily Scrum, due to the fact they locate it really valid place to begin and wish to spend far more time discussing.

Team is too large

If the team is huge then it takes much more time to complete the Every day Scrum. In this case folks complain that the discussion doesn’t pertain to their tasks and want their turn to speak to come swiftly so that they can leave early.

How to deal with problems

Below are some ways to deal with such scenarios:

Proper team training on Scrum

Program proper training for team members or present occasional, little Scrum awareness sessions with the team.

Reiterate the three questions

Reiterate the three questions as many times as feasible to remind the team until the team reaches that maturity level.

Steer clear of a lengthy technical discussion

If an individual tries to explain the technical problem or if it’s taking the shape of a technical discussion, the ScrumMaster must quit them politely and ask to have this discussion offline. Often focus on the present Sprint Backlog whilst discussing tasks.

Scrum of Scrums

In the case of a massive team, take into account a Scrum of Scrums. It really is a lot more powerful for big or distributed teams.


The Every day Scrum assists to improve the individual’s commitment within the team, and the team’s maturity level and self organization. Eventually it creates a self organized team with positive team vibes.


Leave a Reply

Copyright © 2010-2012 Home of Project Manager. All rights reserved.
Focus on project management. Powered by MyPmHome Team.