Daily Scrum

• This is a key inspect and adapt meeting, it is Not a Status meeting
• inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work
• inspect how progress is trending toward completing the work in the Sprint Backlog
• optimizes the probability that the Development Team will meet the Sprint Goal
• Every day, the Developers should understand how it intends to work together as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment by the end of the Sprint
• It is an excellent opportunity to inspect and adapt upon their progress to the Sprint Goal and make adjustments to the Sprint Backlog
• During the Daily Scrum the SG should be the main topic of conversation, creating a plan for the next 24 hours towards that goal; By the end of the Daily Scrum, the team should have a clear plan for the next 24 hours
• Characteristics
  • Participants: Developers are responsible for conducting it, If PO or SM actively working on items in the SB, participate as Developers
    • SM do not need to attend only
      • ensures that the meeting happens
      • teaches them to keep it within the 15-minute time-box
      • If others are present, ensures that they do not disrupt the meeting
  • Time-box: maximum of 15 minutes.
  • Structure
    • Developers can select whatever structure and techniques they want, as long as focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work
      • Example
        • What did I do yesterday to help the team meet the Sprint Goal
        • What will I do today to help the team meet the Sprint Goal
        • Any impediment towards the Sprint Goal
  • Purpose
    • creates focus
    • improves self-management
    • improve communications
    • identify impediments
    • high-light and promote quick decision-making
    • eliminate the need for other meetings: is not the only time Developers are allowed to adjust their plan. They often meet throughout the day for more detailed discussions about adapting or re-planning the rest of the Sprint’s work
• Inputs: SB, …
• Outputs: actionable plan for the next day of work and (potentially) adjustments to the SB needed to reach the Sprint Goal
• Myth: The Scrum Master must be present during the Daily Scrum
  • The myth is that SM is expected to facilitate the Daily Scrum, or be present to pick up impediments
  • According to the Scrum Guide, the Daily Scrum is owned by the Developers
  • Although the Scrum Master can be present to help facilitate the Daily Scrum, this is not required
  • The SM ensures that it takes place, but the Developers are responsible for conducting the meeting
  • Outside of the Developers and potentially the Scrum Master, no other people participate
  • If the Daily Scrum results in decisions that affect others (like the Product Owner), they can be consulted by the Developers afterward
  • Having the Scrum Master present during every Daily Scrum is associated with a number of ‘smells’ that may indicate problems in how Scrum is applied
    • SM acts as a manager, uses the Daily Scrum to distribute work and make decisions
    • The Developers do not support or commit to work with Scrum, and needs the SM to ‘make sure it happens’. the deeper motivation to work with Scrum needs to be addressed
    • Developers depending on the Scrum Master to facilitate. This impedes the ability of the Scrum Team to learn how to self-organize
    • The Scrum Master uses the Daily Scrum to feel meaningful, an opportunity to take the stage and have a visible contribution
  • Tips to make the Daily Scrum more effective (as Scrum Master)
    • Reiterate the purpose at the start
    • Take a (literal) step back placing yourself outside
    • Limit yourself to only asking open questions
    • Limit yourself to only asking questions related to transparency, inspection, and adaptation
    • Don’t actively facilitate the Daily Scrum
    • Don’t attend the Daily Scrum. Observe what happens afterward
    • Ask someone in the Development Team to facilitate
    • Let the Developers choose the starting time and location. This increases the feeling of ownership and encourages the team to start on time