Blog

The latest thoughts and expertise on technology, business, and people.

TOP > Blog Articles > Daily Scrum’s Good & Bad Habits

Daily Scrum’s Good & Bad Habits

press

Daily Scrum is a simple concept to adapt but too many teams practice it to provide status reports to Scrum Master or have it for 1 hour to discuss every single detail.  This is when the team members start to dread the meeting or don’t even remember why they end up standing for so long each day. To avoid the common mistakes let’s look at the Daily Scrum’s good and bad habits:

   Bad Habits:

  • Waiting for team members
  • Replacing Sprint planning and discussing the acceptance criteria, user stories and story points
  • Team members providing too much details like technical fix, Server issue, Jira QA task, explanation about how the Post-it flew away etc.
  • Just relying on Daily Scrum and not having any other meetings to discuss issues, ideas, clarifications and other topics
  • Not asking for help or helping someone on the team
  • Not remembering the 3 Daily Scrum questions every day
  • Not listening to other team members during the meeting
  • Using cellphone, bringing food and other distractions during the meeting
  • Choosing not to attend and then not knowing or asking the team about the progress, issue, and fix

   Good Habits:                                                                   

  • Daily stand-up with timebox of 15-minutes
  • Try to keep it on same time and place each day to reduce complexity
  • Only discuss the following 3 Daily Scrum meeting questions:
  • What did you do yesterday?                                            
  • What will you do today?
  • Is anything in your way from meeting the Sprint goal?
  • Respect each team member’s time by being punctual and don’t disrupt if you arrive late
  • Scrum Master ensures that the Development Team has the meeting
  • For a more detailed and longer discussion, schedule another meeting after the Daily Scrum
  • Scrum Master resolves impediments raised during the meeting
  • This is not designed to be a status for the Scrum Master, Product Owner, Management and Stakeholders, but rather an update and commitment to team members.
  • This meeting is intended for Development team but the dedicated project team members such as the Product Owner and Scrum Master can also attend for transparency.  Other people such as Account Manager, CEO, customer, management, team members from another project, VP etc. can attend the meeting as a spectator only and the Scrum Master should make sure that they don’t disrupt the team during the meeting.

Overall, Daily Scrum increases team collaboration, transparency, teamwork and minimizes impediments. A Scrum team that follows correct Daily Scrum meeting practice will be more successful in achieving results, adaptable to change and work effectively as a team.  

Pallavi Tiwari    

 

Back to list