Smoother and Faster Scrum Poker Planning.

Plan and estimate your projects seamlessly with free Scrum poker rooms. No ads, no costs, just create an instant room and make your planning easier

1. Preparation

Before the Scrum Poker session, the product backlog should be ready, and user stories or tasks that need to be estimated are identified. These user stories should have been well-defined and broken down into smaller, manageable pieces.

2. Team Setup

The Scrum team, including the Product Owner, Scrum Master, and development team members, gather for the estimation session. The ideal team size is usually between five to nine members to ensure effective collaboration.

3. Estimation Process

The Scrum Poker session typically starts with the Product Owner or Scrum Master presenting a user story or task that needs to be estimated. Each user story is discussed to ensure that all team members understand its requirements and scope.

4. Poddle Poker

To facilitate the estimation process, you can create a room and share the link with our team. If you have trouble to find a timeslot for your session. You can try out our Doodle alternative at poddle.network

5. Individual Estimation

Once the user story is understood, each team member privately selects a Planning Poker card representing their estimation of the effort required to complete the task. The results are hidden until the estimation round is complete.

6. Reveal and Discussion

After everyone has chosen a card, the results are displayed by a button click. If there is a consensus (i.e., all team members selected the same card), that becomes the final estimation.

7. Discussion of Divergent Estimations

If there is a wide range of estimations, the team engages in a discussion to understand the reasoning behind the various estimates. This discussion helps identify any misunderstandings, risks, or additional considerations related to the user story.

8. Re-Estimation (Optional)

Based on the discussion, team members may revise their initial estimations and select new cards. The process of discussion and re-estimation continues until a consensus is reached, or until the team decides to escalate the issue to the Product Owner for clarification.

9. Recording the Estimations

The final estimation agreed upon by the team is recorded for the user story. It's important to document these estimates for future reference, planning, and tracking progress.

10. Next User Story

The process continues with the next user story or task in the backlog until all items are estimated.