The Daily Scrum (also referred to as the “Stand-up”) is one of five events in Scrum. Many people use this event to provide a status report to the Product Owner or Scrum Master, and even to stakeholders, but this event plays a more critical part in ensuring that the team continues to stay focussed on their goal and adapt their work so they improve their chance of achieving it.
Like every event in Scrum, the Daily Scrum is all about empiricism. Its purpose is for the team to inspect its progress toward the Sprint Goal and to adapt the Sprint Backlog so that its plan for achieving the goal is made transparent to everyone.
This event is purely for the people doing the work – the agile team.
The governance of Scrum reinforces that the team should be self-organising and no one outside the team should be telling them how to create their Increment of work. As such, only the team meet during the Daily Scrum. If the event needs facilitating, then the Scrum Master attends. But if he does, be careful that the Daily Scrum doesn’t turn into a status report.
The Daily Scrum is held every day of the Sprint. At it, the Team plans work for the next 24 hours. This optimises team collaboration and performance by inspecting the work since the last Daily Scrum and forecasting upcoming Sprint work. Importantly, it’s a good idea to hold the Daily Scrum at the same time and place each day to reduce complexity.
If the event isn’t held daily, empiricism suffers. The team loses the ability to inspect its progress and make necessary changes to their plan as reflected in the Sprint Backlog. Ultimately, not holding a Daily Scrum every day increases the risk that the Sprint Goal could be put in jeopardy.
The usual pattern for people to run a Daily Scrum is for each team member to answer three questions:
Unfortunately, this pattern quickly turns the event into a status report. When people are transparent and collaborating continuously, this form of the Daily Scrum seems to make the event irrelevant. Many people just hate the Daily Scrum as a result. Instead of turning the Daily Scrum into a report to Mum, try these actions instead:
If this takes only 5 minutes, then head back to work.
How do you write great User Stories?
Backlog Refinement is a critical part of good practice in Scrum. Refining the Product Backlog ensures that the Team and Product Owner have sufficientl
Should you have business as Product Owners? Is the Release Train Engineer a Delivery Manager? Where do Project Managers go? Aren’t Epic Owners the executive? Everyone gets these things wrong. Find out how to avoid SAFe’s implementation traps.
Are you still asking the ‘three questions’. It’s time you learned some better patterns to inspect your progress toward the team’s Sprint Goal.
You have reports to deliver to executive. Delivery, risk, and cost is foremost on their mind. What kind of reports on your agile capability and delivery, based on objective agile project management metrics, are going to provide you with the best transparency of what’s really going on?
The market is full of agile project management metrics tools that help with on-time and on-budget delivery, but where are the tools that help coaches and consultants understand how to scale agile capability development? Do existing tools do the job well enough?
Copyright © Zen Ex Machina® and ™ (2021). All rights reserved. ABN 93 153 194 220