The purpose of this discussions is to explore the challenges that the community has faced with Daily Stand-ups, and to understand ways that you overcame them. (in or out of the box) I also have a few questions at the end, related to the structure of the stand-ups.
There are several certifying organizations with similar definitions for the Stand-up event...meeting. (Okay that was on purpose. I wanted to make some Agile heads explode.) I am not sure why, but it does; even though the scrum guide refers to it as a meeting numerous times.
I have included a few below:
Scrum.org - Daily Scrum: daily time-boxed event of 15 minutes for the Development Team to re-plan the next day of development work during a Sprint. Updates are reflected in the Sprint Backlog.
Scaled Agile, Inc. - Coordinating with Daily Stand-Up Meetings Each day, the team has a formal event—the Daily Stand-up (DSU) meeting—to understand where they are, escalate problems, and get help from other team members. During this meeting, each team member describes what they did yesterday to advance iteration goals, what they are going to work on today to achieve the iteration goals, and any blocks they are encountering in delivering iteration goals. As this is a daily coordination meeting, the Scrum Master has to keep it short and to the point. The DSU should take no more than 15 minutes and is done standing up in front of the storyboard. But team communication does not end there, as team members interact continuously throughout the iteration. Facilitating such communication is the main reason why ScrumXP prefers that the team be collocated whenever possible. © Scaled Agile, Inc.
Then comes the three questions, and don't deviate!!! (Agile gods get angry)
I have found that the Agile community can sometimes be very rigid, even dogmatic about maintaining the structure of this meeting.
As Development Teams, is it time that we rethink the structure of the meeting, maybe even retool it? I have encountered some Scrum Masters that were more interested in adherence than information radiation, or meaningful communication among the team. Meaningful is subjective I know, but isn't that for the Development Team to decide?
Consider how the Scrum Guide defines this meeting.
The Scrum Guide defines this meeting's use as, "to inspect progress towards the Sprint Goal, and to inspect how progress is trending toward completing work in the Sprint Backlog."
The Scrum Guide also says that, "The structure of the meeting is set by the Development Team and can be conducted in different ways if it focuses on progress toward the Spring Goal. Some will use questions, some will be more discussion based." It then suggest the three questions, which have now become mainstream.
My questions for the Community is,
I look forward to hearing your thoughts!
Introduction In this article we describe the complexity of managing release cycles of complex IT solutions that comprise of a number of Apps, Service and/or Microservices. In particular, we will tou...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events