3pts.dev is a free online Scrum poker tool (similar to Planning PokerŪ) for remote agile teams. Estimate
agile effort or relative size of user stories, also known as story points, or complexity. Start by
creating a room and sharing the link with your team. Everybody joins from their web browser. The Scrum
Master (moderator) shares the story description on Zoom, Microsoft Teams, Slack or on a screen projector.
Every team member votes with a story points estimate, relative to the anchor story which the team
collectively agreed on. The most important feature of 3pts.dev is that users cannot see other votes until
everybody has voted or the moderator has shown the votes. This is a core requirement for a successful
agile poker session. No email or signup required.Try It Now
Planning PokerŪ is a registered trademark of Mountain Goat Software, LLC. 3pts.dev is not associated with or sponsored by Mountain Goat Software, LLC.
The Fibonacci number sequence is a common story points estimation scale because it captures the uncertainty in relative complexity estimation. Story points represent how one story compares to an already estimated anchor story. The Fibonacci sequence represents "buckets" that you can place similar stories into, without being too specific about the exact amount of time the implementation will take. However, the Fibonacci sequence also includes the numbers 21, 34, 55 and 89 which may be confusing when comparing stories to others. Hence, Agile teams often choose the Scrum card sequence which replaces these numbers with the more familiar 20, 40 and 100. For even more high-level and uncertain estimation, teams may choose "T-Shirt Sizing" and estimate stories with letters instead of numbers. 3pts.dev supports Scrum, Fibonacci and T-Shirt size card sequences and the moderator can select the desired one from the gear icon.
During sprint planning the agile team uses a tool like 3pts.dev to assign story points to a story relative to the anchor story (or stories) which the team has collectively agreed on. The anchor story may be one that the team has already implemented or a fictitious feature, however it should cover multiple system components and be easy to describe. During planning poker the Scrum master asks: how complex is this story relative to the anchor story? Every team member chooses a card and submits their vote. When everybody has voted the Scrum master shows all votes. The team discusses until they reach a consensus on the story points estimate. In 3pts.dev remote teams can submit their votes without being influenced by votes of other team members which makes the estimation more accurate.