The Scrum approach to agile software development marks a dramatic departure from waterfall management. Scrum and other agile methods were inspired by its shortcomings. Scrum emphasizes collaboration, functioning software, team self management, and the flexibility to adapt to emerging business realities.


The Daily Scrum; It’s a Good Habit to Make

Posted by admin under Agile and Scrum, Scrum Basics, Scrum Transitions

When you think of the word “habit” what do you think of? In the dictionary, there are several distinctly different meanings for “habit” such as:
1. A customary practice or use
2. An acquired behavior pattern regularly followed until it has become almost involuntary
3. An addiction, especially to narcotics
4. A dominant or regular disposition or tendency; prevailing character or quality

We tend to think of “good” habits or “bad” habits. When the behavior we are repeating results in positive circumstances, it is “good”. When it leads to negative results, addictions etc. it is “bad”.
The “daily scrum” is the heartbeat of scrum and is a “good habit”. Tamara Sulaiman, a Certified Scrum Trainer, in her blog post titled “Techniques for Improving Your Daily Scrum; when Your Daily Scrum isn’t Daily” says, “The daily scrum is one of the most valuable practices that any team can use.” The purpose of the daily scrum is to increase the team’s communication and focus by answering 3 questions, “What have I accomplished since the last meeting? What do I plan to do for the next meeting? What impediments are in my way? “ When teams don’t huddle daily, they risk losing the communication, focus and momentum of a team necessary to build the right product with the appropriate quality on time. Oftentimes, teams will have excuses for avoiding the daily scrum or stand up meetings. I’m sure you will be familiar with many of the excuses Tamara talks about. The daily scrum, however, makes teams more successful because it is the smallest, tightest feedback loop built into the Scrum framework. Think of it like brushing your teeth or exercising daily– it’s a good daily habit to make and will pay off in the long haul.

Comments Feed

Reader's Comments

  1. Ken Bradshaw |


    I don’t know if you want to take the time to quantify it. But look for the reduction in obstacles on a daily basis. And for the increased collaboration.

  2. brainEater |

    Technology oriented people are mostly introverts. They also tend to look for technical solutions to any problem. By these two traits they could easily slip from reality and start to build their own reality/software. It would be perfect for them, but could be completely useless for customer. Daily scrum allows them to remain “connected”. In waterfall project checkup meetings are 1/week or even 1/2weeks. In case that you miss their slip at one meeting and realize it the second one, you will loose 2 weeks or even a month. That’s a lot and I’ve seen even longer period. Daily scrum reduces this to 1-2 days. And as the people are more communicating they realize each other weaknessis. All of us has some. And in a team they could be addressed and covered by other members.

    Something to though: Could you imagine marine fire squad that train together only 1 day a week?

  3. NoMatter |

    Where can we find some quantitative evidence proving that the daily scrum meeting for software development increases the productivity of individuals?
    Or is the use of daily scrum better in the context of escalations, i.e. reducing bug backlogs.
    What happens when the daily scrum is used as another additional tool for software development *in addition to* meeting with relevant team members for discussing design details?
    When does daily scrum turn into political tool to keep team members on their toes and possibly lead the team away from effective cooperation and into the realm of competition?

Leave a Reply

Reload Image

Scrum Training Courses