+91-7710033016 / +91-8291749529 support@effectivepmc.com

Common Misconceptions and Negative implications

Most teams conduct Daily scrum as a status meeting. When this happens, following negative implications result

  • Dev Teams start thinking that this is Scrum Master’s forum
  • Dev Teams don’t take accountability
  • Dev Teams lose interest and start saying “there is nothing to status report every day”


  • Primary intention of Daily Scrum is to Inspect and Adapt. This is supposed to be a forum where the Dev Team finds out if things are going in the right direction. If they are not, then it is time to discuss the same and adapt as soon as possible. If required, the scope needs to be adjusted, decisions need to be taken so that the Dev Team comes back on track.
  • It is good to keep the “Sprint Goal” at the centre when the Daily Scrum discussions are on. This is not about day-to-day tasks. This event is about knowing if we will be meeting the “Sprint Goal” or the business objective.
  • The three questions (while they are not compulsory in Scrum) actually are mis-understood by most teams. The three questions are not about “What did you do?”, “What are you going to do?”, “What are your impediments?”. The tree questions are about Sprint Goal and not about what tasks you are doing . So the correct 3 questions are

· What did I do yesterday that helped the Development Team meet the Sprint Goal?

· What will I do today to help the Development Team meet the Sprint Goal?

· Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?

  • Daily Scrum is also an important opportunity for collaboration for the Dev Team. Scrum Master is actually a facilitator in this forum. Scrum Master’s job is to make sure
    • The Daily Scrum happens
    • Negative things which happen regularly are prevented
    • To make sure that it finishes off on time within 15 minutes and teams are free to go back to work.
  • The only mandatory participants of Daily Scrum therefore are the Dev Team members and not Scrum Master and Product Owner. PO if at all joins,  his presence is limited to clarifying scope.