There Is No Classic Status Meeting in Scrum

Are you surprised? Let's take a look at particular scrum meetings...
Daily Scrum (Standup Meeting)
Everybody knows this guy, right? That's the easiest one where the ScrumMaster asks people one by one what they did yesterday and what they're going to do today. Perhaps because he wants to inspect their work... What if I told you that this is an agile anti-pattern? 
The real purpose of the daily scrum is to take a short break and make sure that we're still moving toward the sprint goal and we still believe that we can deliver the sprint goal before the sprint ends. Thus we're not interested in how are people spending their time. Instead we focus on what has been completed and how we're going to collaborate in order to get done what needs to be done. 
Sprint Review
The next is sprint review meeting where the anti-pattern is to present which particular user story has been finished and which has not. Some teams brought this status to perfection and they had slides and charts and tried to evaluate success of the sprint. I had this experience personally. 
But the purpose of sprint review is to demo the Potential Shippable Product Increment - which is what the team has finished - to the customers/stakeholders. The feedback is then an important input to the backlog refinement and helps to deliver successful product. 
Sprint Retrospective
The last one is sprint retrospective where the anti-pattern is to check action items form the last retrospective and to evaluate how they were implemented and how they worked for particular problem. 
But the retrospective is supposed to be a creative workshop where the team thinks about what they want to change, what is fine and what has to be improved. To make this working the team have to be able to take a look at things from outside. If you begin with status the outer image is gone and you will find yourself just repeating what left from the past. If you feel that things are not moving forward it will be said on the next retrospective for sure even without repeating old action items.
Freely translated from Zuzi's blog 12/23/16

Komentáře

Okomentovat

Populární příspěvky z tohoto blogu

Yesterday's Weather Rule

A legend says that there was a government that spent millions of dollars on a weather prediction satellite. After a big effort and long time they developed a thing that was able to accurately predict the weather with 70% success rate. It was quite good until somebody realized that if they simply said that today's weather will be the same as yesterday's weather they'd also have the accuracy of 70%. The idea is that you can predict what's gonna happen from what already happened. In the scrum process, this principle helps us to avoid overcommitting. The rule says "Don't take more to the next sprint than you delivered in the previous sprint". It can perfectly happen that the team cannot deliver the whole sprint commitment. But it is very important to take appropriate steps in order to keep this problem under control. And applying the yesterday's weather rule is the basic thing that you can do. Just reduce the sprint commitment of the next sprint to the ...
Další informace

Three Levels of ScrumMaster

Scrum defines three roles. ScrumMaster, Product Owner and Development team. While it is easy to understand the PO and dev team role, to understand the ScrumMaster role can be challenging even for ScrumMasters. ScrumMaters are building self-organized teams. But what ScrumMaster does when the team is already self-organized? Let's take a look at a concept of three levels of the ScrumMaster as it it described in the Great ScrumMater: #ScrumMaster Way book. Level #1 - My Team ScrumMaster at this level feels responsibility for his team. The goal is to build self-organized team and to let people embrace the agile mind set. It sounds easier than it is. As a beginner the ScrumMaster can be even struggling with questions like "How can I make myself useful everyday?". But the goal is a long-term activity and the SM should actually suppress the urge to do something, i.e. give advice, propose a solution etc... The first step for SM should be to make himself comfortable in observi...
Další informace

Tribal Culture and Leadership in Agile Environment

The concept of tribal culture in an organization was introduced in the book  Tribal Leadership . It is quite interesting theory and from the agile environment perspective it has a new and important dimension. Let's have a look and put things together.  A tribe is a group of people that have something in common. In an organization trying to set up agile environment, we can easily imagine a scrum team. But we also have the community - a team of teams. Then there are virtual teams like a team of scrum masters, product owners or managers. The whole business groups... We can identify tribes at basically every scale.  A tribal culture is the dominant culture that can be observed in a group of tribes. Or in an organization. The culture can be described as 5 stages. Let's explore these stages and then we will have a look at what it means for us. Stage #1 - Life Sucks A culture of individuals with no hope. Everybody is alone in such culture. This is a culture of prisons a...
Další informace