Introducing IPM Poqer: a planning poker tool
In software development world, effective project management and accurate estimation of tasks are crucial for delivering successful products. One popular technique that has emerged to facilitate this process is Planning Poker.
This collaborative estimation method not only enhances accuracy but also fosters team engagement and communication.
The goal of this method is to estimate the effort or complexity of tasks, a consensus-based technique used in software development. It help teams reach a shared understanding of the work involved in a project.
The software we used to do planning poker named pointing poker.Once a consensus is achieved, the final estimate is recorded for the user story or task, and the team moves on to the next item.
As a web developer, I want try to re-create this software. It simple enough to create and can be finished with no much time. The problem are:
Communication Challenges
Before the session, the team prepares a list of user stories or tasks that need estimation. Each team member should have a deck of Planning Poker cards, which usually contain a sequence of numbers representing effort estimates (commonly Fibonacci numbers: 1, 2, 3, 5).
The team discusses each user story or task to ensure everyone understands the requirements and scope. This discussion is crucial for clarifying any ambiguities and aligning the team's perspective.
After the discussion, each team member selects a card from their deck that represents their estimate for the task. The cards are revealed simultaneously to avoid influencing each other's estimates.
If there is a significant discrepancy in estimates, the team discusses the reasons behind their choices. Team members with the highest and lowest estimates explain their reasoning, allowing for a deeper understanding of the task's complexity.
After the discussion, the team may re-estimate the task, repeating the process until a consensus is reached. This iterative approach helps refine the estimates based on collective insights.
Once a consensus is achieved, the final estimate is recorded for the user story or task, and the team moves on to the next item.
Solution
To address communication between participants, I am implementing WebSocket technology. For the backend, I am using Ktor, while the frontend is built with Remix, a React framework.
The project manager (PM) will control when the story is presented to the participants and when the points are revealed to the team members.
That’s it! I am developing this tool, named IPM Poqer, as a gift to the community, and I do not charge anyone for its use.