Saturday, September 22, 2018

The sprint planning meeting that goes on forever | SupremeAgile


The sprint planning meeting is the longest meeting in the scrum framework and based on my experience it also the most exhausting meeting for most teams. The most difficult thing about this meeting is that team members often come to this meeting with the mindset that it will take the exact time written in the book…but it doesn’t!

In scrum we have a very important term called timeboxing. A time box is an agreed upon and limited box of time that is used by a person or team to perform a dedicated activity (see here for more information about timeboxing). Everything in scrum is time-boxed, including the scrum planning meeting, so what happens when the meeting time is near the end, and the team hasn’t determined the goal or sprint backlog? Do we end the meeting and continue it next week? Should we extend it? Do we just end it?

This scenario happens over and over, especially for new scrum teams that have neither the maturity nor the experience to conduct an effective sprint-planning meeting. So, what should one do in this scenario? To be honest, it really depends on what you want to achieve, but some common solutions that I love to use are:

Let the team learn the hard way

Let’s say that you have a team that is not willing to change their habits and continuously ignores the meeting’s timeframe. In this case, you can cut the meeting at the end of the time box, which will make the team suffer throughout the entire sprint. The ritual is that once you recognize that the team will not finish in time, you can address the team and let them know that the meeting ends in 10-15 minutes and let them choose whether to start the sprint with what they have or start all over again the next day (what do you think they will choose...?).

Extend the meeting and ignore the time-box

Another option is to ignore the fundamental foundations of agile and just extend the meeting while ignoring the meeting timebox. Based on my experience, if you do it once, it may help the team finish the meeting with a good feeling, but once the team makes it a habit it's a red flag for a much deeper problem.

During my many years as an agile consultant, I worked with hundreds of agile teams, and one thing that I know for sure is that you cannot let the team drag on the meeting. It usually doesn't help accomplish anything. People are tired and lose their ability to focus. If they failed to do an effective planning during the meeting, which can go from two to eight hours (depending on the length of the sprint), the chances are that the team won't manage it given the extension.

Another day, another chance

Another commonly used option is to re-schedule the meeting for the next day. In my opinion, it's the last option that I will use but still an option. If you decide to re-schedule the meeting, you must ensure that it does not become a regular solution for the team. You must perform a deep root-cause analysis (RCA) to understand why the team fails to deliver within the meeting time frame.

Summary

Each one of the solutions above is valid for specific cases, but to cut it short, no matter what option you use, the team must learn to conduct the sprint-planning meeting effectively as we expect to see in scrum. Make sure the team understands the importance of timeboxing so they can respect and follow it during the day to day activities. 

Thanks to Tally Helfgott for proofreading :) 

Linkedin Profile

No comments:

Post a Comment

My Presentations