How Planning Poker works

1. The Product Owner or facilitator presents a user story.

2. The team discusses the requirements and asks clarifying questions.

3. Each team member privately selects an estimation card.

4. Everyone reveals their cards at the same time.

5. If estimates differ significantly, team members explain their reasoning.

6. The team discusses and votes again until a consensus is reached.

Common Planning Poker score scales

Several estimation scales are commonly used in Agile:

• Fibonacci Sequence (most popular)

  • 1, 2, 3, 5, 8, 13, 21, 34, 55, 89

  • The increasing gaps reflect the growing uncertainty of larger tasks.

• Modified Fibonacci

  • 0, ½, 1, 2, 3, 5, 8, 13, 20, 40, 100

  • A simplified variation used by many Scrum teams.

• T-Shirt Sizes

  • XS, S, M, L, XL, XXL

  • Useful for high-level estimation before breaking work into smaller stories.

• Linear Scale

  • 1, 2, 3, 4, 5, 6, 7, 8, 9, 10

  • Suitable for teams with relatively small, similarly sized tasks.

• Powers of Two

  • 1, 2, 4, 8, 16, 32, 64

  • Another relative estimation approach that emphasizes increasing uncertainty.

• Bucket System

  • Stories are grouped into buckets such as Small, Medium, Large, or into numbered categories. free top games

  • Commonly used when estimating a large backlog quickly.

Planning Poker (often called "Pokering" in Agile discussions) is a collaborative estimation technique used by Agile teams to estimate the effort, complexity, or size of user stories. Each team member selects a card representing their estimate, and all cards are revealed at the same time to avoid influencing each other's opinions. If estimates differ significantly, the team discusses the reasons and votes again until a consensus is reached.

The most common scoring system uses the Fibonacci sequence because uncertainty increases with larger tasks. Typical values are 1, 2, 3, 5, 8, 13, 21, 34, 55, and 89 story points. Some teams also use XS, S, M, L, XL, T-shirt sizing, or a simple numeric scale such as 1–10. The 1000games goal is not to estimate exact hours but to compare the relative size and complexity of work items.

Common sizing scales are usually Fibonacci numbers like 1, 2, 3, 5, 8, 13, 21 because task complexity tends to grow non-linearly. Some teams also use Baseball Bros T-shirt sizes (S, M, L, XL) for rough estimation.

Hahaaa

Great question! Pokering in Agile, often referred to as “Planning Poker,” is a collaborative estimation technique used by teams to determine the effort required for project tasks. It’s a fun way to engage everyone, facilitate discussion, and reach a consensus on project work.

In Agile, “pokering” refers to Planning Poker, which is a consensus-based, gamified technique used by Agile teams (especially in Scrum and Extreme Programming) for estimating the effort or relative size of development work, typically user stories.