How to use planning poker as effective agile estimation technique
Planning Poker serves as a consensus-driven, gamified method for estimating efforts or the relative size of development tasks, primarily applied in software development. This comprehensive article delves into the effective utilization of Planning Poker as an agile estimation technique.
Understanding Planning Poker
Planning Poker is a collaborative approach to determine estimates or the 'size of work' for a team-assigned task. In this consensus-based technique, team members individually cast their votes for the estimate, and the entire team collectively finalizes the estimation. Widely employed in software development, particularly in agile frameworks like Scrum and extreme programming, Planning Poker fosters teamwork and effective estimation.
Historical Background
James Grenning initially designed Planning Poker, and its popularity surged under the trademark of Mike Cohn. Grenning's original paper on Planning Poker can be found here.
Research from the Rand Corporation in the 1940s revealed the inherent challenge humans face in accurately estimating hours, a difficulty consistently observed in practical experiences. Planning Poker addresses this challenge by providing relative estimates that consider factors like risk, uncertainty, and complexity.
Relative Estimates
Planning Poker generates relative estimates, emphasizing the size of work rather than precise, absolute figures. Unlike construction projects with well-defined tasks, software development involves hidden complexities that surface progressively, making accurate hour-based estimates challenging.
Versatility of the Technique
While rooted in the Wideband Delphi method, Planning Poker's adaptability extends beyond software development. This consensus-based approach can be applied to estimate various scenarios, such as predicting stock market trends or forecasting a country's population. A panel of experts provides individual estimates, engages in debates, and reaches a consensus on the final estimate.
Value Added by Planning Poker Estimation
Predictability, not pinpoint accuracy, is the goal of estimation.
Story points aid in sprint planning, ensuring achievable team commitments.
Establishing a common understanding of tasks and uncovering biases.
Filtering both pessimistic and optimistic estimation biases.
Revealing hidden assumptions and sharing insights within the development team.
Facilitating active participation and learning for each Scrum team member.
Implementation Timing
Planning Poker can be employed during product backlog refinement or sprint planning meetings. Stories can undergo multiple evaluations, especially if initially estimated at higher levels, prompting the need for splitting into smaller tasks.
Physical vs. Online Planning Poker
In co-located environments, using physical planning poker cards during discussions is recommended. These cards include unique elements like the Infinity card, Question card, and Coffee Break card.
In essence, Planning Poker stands as a valuable technique, emphasizing collaboration, adaptability, and effective estimation within agile frameworks and beyond.
