Agile Wednesday
How to implement Planning Poker in 3 easy steps? Explanation via Case Study.
Case Study
Planning Poker at Tech Solutions Inc.
Background: Tech Solutions Inc., a mid-sized software development company, was working on a new project management tool. The team consisted of developers, QA testers, UX designers, and a product owner. They decided to use Planning Poker to estimate the effort required for various user stories in their backlog.
Steps:
Preparation:
The product owner, Sarah, prepared a list of user stories for the upcoming sprint. Each story included detailed descriptions and acceptance criteria.
Team members were given Planning Poker cards with values based on the Fibonacci sequence (1, 2, 3, 5, 8, 13, etc.).
Discussion and Estimation:
Sarah presented the first user story: “As a user, I want to be able to create a new project so that I can manage my tasks.”
The team discussed the story, clarifying any doubts and considering potential challenges.
Each team member then privately selected a card representing their estimate of the effort required.
Reveal and Consensus:
All team members revealed their cards simultaneously. The estimates ranged from 3 to 8 story points.
The team discussed the reasons behind their estimates. John, a developer, thought it would take 8 points due to potential integration issues, while Lisa, a QA tester, estimated 3 points, considering only the testing effort.
After discussing and addressing concerns, the team re-estimated. This time, most members agreed on 5 story points, reaching a consensus.
Outcome: Using Planning Poker, Tech Solutions Inc. was able to:
Improve Accuracy:
The collaborative discussion helped uncover hidden complexities, leading to more accurate estimates.
Enhance Team Collaboration:
The process encouraged open communication and knowledge sharing among team members.
Boost Morale:
The interactive and inclusive nature of Planning Poker made the estimation process engaging and fun
#agile #projectmanagement