Top 5 Mistakes to Avoid in Scrum Poker / Planning Poker Sessions

Scrum poker, also known as planning poker, is a widely-used method for estimating the effort required to complete a task in a Scrum project. It involves a team of developers, product owners, and other stakeholders working together to estimate the complexity and effort of a task or feature. While Scrum poker can be a very effective tool for project planning, it is not without its challenges. In this blog post, we will discuss some common mistakes teams make when using Scrum poker and how to avoid them.

1. Not understanding the purpose of Scrum poker: The purpose of Scrum poker is to provide a quick and accurate estimate of the effort required to complete a task. It is not a negotiation or a bargaining tool. Team members should come to the meeting prepared and ready to provide an honest estimate of the task at hand.
2. Not involving the right team members: Scrum poker is a team activity and it is important to have the right people in the room. This includes developers, product owners, Scrum masters, and other stakeholders who have a good understanding of the task at hand.
3. Not allowing for discussion: One of the key benefits of Scrum poker is the ability to discuss the task and come to a consensus on the effort required. However, some teams make the mistake of not allowing for discussion or debate. It is important to encourage team members to share their thoughts and reasoning behind their estimates.
4. Not using the right cards: Scrum poker uses a deck of cards with numerical values to represent effort. These cards should be easily understood and consistent across the team. Using a different deck for each sprint makes it difficult to compare estimates and evaluate the overall productivity of the team.
5. Not updating the product backlog: After the Scrum poker meeting, it is important to update the product backlog with the estimates for each task. This will help the team track progress and make adjustments as necessary.

To avoid these common mistakes, teams should make sure to understand the purpose of Scrum poker, involve the right team members, allow for discussion, use the right cards, and update the product backlog. By following these guidelines, teams can improve the accuracy and efficiency of their project planning and increase the chances of success.

Additionally, incorporating techniques such as using story points, considering shirt sizes for task estimates, and involving the Scrum Master and Product Owner in the planning sessions can enhance the effectiveness of Scrum poker. Understanding the concepts from experts like Mike Cohn and utilizing tools can also provide valuable insights into making your planning poker sessions more productive.