Lets talk about one of the most important meetings in the Scrum framework: the Daily Scrum. It is, as the name says, hold on every day of the Sprint (ok, just on the working days :D). In the daily the team comes together to find out how the Sprint is going, what could be a risk to not reach the Sprint Goal and how to prevent not finishing the most important stuff. With important stuff here is ment the things which give the most business value.
The famous three questions
The most frequent thing you hear or read about the Daily Scrum (e.g. the Scrum Guide) are the following three questions every team member should answer:
- 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?
Lets have a short look who you need in a Daily Scrum. At least you need the team members (not the whole Scrum Team). Often it is good to have the Scrum Master and the Product Owner there too. The Scrum Master can give hints how to handle certain issues or point out risks which the team is not seeing. Also she can help the team focus more on improtant and necessary stuff. So for instance he can point out, that the team is premature optimizing a not yet proven solution or not focusing on customer needs any longer. The Product Owner can be a listening and answering part of the Daily Scrum.
Three questions – the dark side
The risk with the “three questions Daily Scrum” is, that the team is just doing a report. If your company has the structure, that the Product Owner is also the boss of the team, chances are high, that the team is not selforganizing and swarming around the problems, but just looking direct into the eyes of the Product Owner/boss and reporting to him. They will tell him what they have done and what will be done next. But even if there is no such structural antipattern the risk of unseen risks is given in this approach of the Daily Scrum. This risk comes with the three questions, which are easily mistransformed to the following questions:
- What did I do yesterday?
- What will I do today?
- Do I see any impediment?
Maybe you see what happened? We completely lost the focus on the important part, the Sprint Goal. The questions are sounding very similar. If you don’t look, or better listen, carefully, it seems alright, that the team answers the shorter questions. But: without the focus it is very probable, that the team forgets fast which reason they have: the “Why?”, the “What for?”. The team lost the focus on the customer needs. Now the team can fill the fifteen minutes of Daily Scrum with unimportant chat. They can seem very busy and look like hard working, but can achieve no business value at all.
Other reasons for hidden risks can be fear or shame. If somebody isn’t feeling safe, she can come into the state of fear, that is the obvious way and shouldn’t need further discussion. The other way it is possible to become fearfull, if you have a hidden or personal goal. For instance you want a raise or a promotion. Than some colleagues tend to bury their mistakes deep under a mile of talking about nuts and bolts all the time. If somebody is ashamed, because she can’t solve a problem, the same can happen. Important here is transparency and security. Work into the why and fix it as deeply as possible!
Why Daily Scrums?
Short break and remember whatfor we do have Daily Scrums: we want to assure, that we reach the Srpint Goals. Therefore we plan on a very small scale what to do next. And we want to identify handle risks as early as possible. With this early access to the risks, we can plan the Sprint as safe as possible. Back to the How!
How to organize an efficient and effective Daily Scrum
The approach i am writing about is based on Eric Brechners presentation. He is talking about Kanban, but that’s no problem. I tried it with some teams and had great results. The teams were focused on the most important things nearly all the time. It is really simple: everybody answers just the questionAre there any risks or problems for reaching our goals?
- Are there any risks or problems for reaching our goals?
The focus is just on the things which can go wrong or are already going wrong. First we decide, if it is an important issue. If it is not solvable on the spot, we don’t talk through the solution at all. We focus on the second question:
- Who will solve this issue with whom?
You can decide to go person by person, story by story or just throwing the question into the room. Just figure out, what works best for the team. In my teams we only asked into the room and gave everyone a look. Normally every issue came out on their own, only sometimes a question about a topic was needed to see the risk.
Later we realized that focusing only on problems, issues and risks is a bit demotivating and we added “Are there joys or are you proud on something?”. That made the Daily Scrum much more fun!
Have you tried this method for Daily Scrums? Or the three questions mentioned in the beginning? Or a completely different method? Let us know and write a comment!
As always i hoped you liked it, thanks for reading and sharing!