5 reasons sprint planning doesn't go perfectly10 Dec 2012
Original post can be found at It-Eye
There are many reasons why sprint planning sessions don’t go the way you want them to. Here is my short list of the things that I have seen breaking the sprint planning sessions the most.
- No Product Owner or not available
Not having a Product Owner available in sprint planning is a bad idea. Even if your user stories are written well there are always questions or decisions that need to be made regarding the functionality or the priority. A solution is to have one other team member be the substitute Product Owner as long as he/she collaborates with the Product Owner and is allowed to make decisions.
- Discussions are too technical or go in to too much detail
Most of the teams are very technically oriented, this means that they often tend to dive into discussions about the technical solution because that is their expertise. This is not a bad thing per se but these discussion often tend to be long, they don’t contribute anything to the sprint planning and can be done later when needed. Solution to this is not to allow technical discussions or have them on a high level instead of talking about all the details.
- Vague user stories
Having vague user stories is one of the worst things you can have in a sprint planning. These user stories don’t allow the team to focus on planning but lets them wonder about what is meant and always bring up discussion where in the end the product owner needs to explain what is needed. In this process a lot will be said but most of the time this information eventually gets lost and is a waste of time. Creating well written stories that have a summarized self explanatory title and a clear scope with explicit points of functionality explaining what is expected and what not helps avoiding these discussions.
- Team members not understanding planning poker
There tend to be two problems here, one is about not understanding how planning poker works and can be fixed by practicing. The second problem is where people don’t know what to take in to account when voting. These people tend to use different criteria when voting and making the planning variate a lot. Possible solution to this problem is creating a short list of criteria points to think about when voting.
- No decisions are made
Having discussions is a good thing but having endless discussions is a bad thing. Sometimes teams keep talking without deciding what to do or how to do it because there is no one to make a decision or wanting to take the responsibility. To fix this problem have the Product Owner make decisions directly when talking about functionality, the priority and the goal. For making technically related decisions point one of the team members as Technical Lead and give them the right to make an decision when needed.
Although the upper list shows the things I have seen go bad in sprint planning I have also seen the same things work very well in some teams. Bear in mind that this is a list of common mistakes but that everything depends of the context and the way you work.