Frequently Asked Questions

What is Planning Poker?

Planning Poker, also known as Scrum poker, is a collaborative estimation technique used in agile project management. It is commonly used by Scrum teams to estimate the effort or relative size of user stories, tasks, or backlog items during the sprint planning process. The method involves team members using a deck of cards with numbers representing story points or relative effort, and through a discussion, they collectively assign a value to each item based on their understanding and expertise.

What is a Planning Poker room?

A Planning Poker room, refers to a physical or virtual space where the Scrum team gathers to conduct the Planning Poker sessions. It can be a meeting room, an online collaboration tool, or any other designated space where team members can participate in the estimation process comfortably. The poker room provides an environment for open communication and collaboration among team members, allowing them to collectively determine the effort required for each backlog item.

Which scale is typically used in Planning Poker?

The most popular scale in Planning Poker is the Fibonacci sequence, which includes numbers like 0, 1, 2, 3, 5, 8, 13, 21, 34, 55, and 89. While this is the go-to choice for many teams, there are alternative scales such as T-shirt sizes (XS, S, M, L, XL, XXL), a modified Fibonacci scale (0, 1/2, 1, 2, 3, 5, 8, 13, 20, 40, 100), a linear scale (1, 2, 3, 4, 5, 6, 7, 8, 9, 10), double-doubling (1, 2, 4, 8, 16, 32, 64), and a Fibonacci-like scale (0.5, 1, 2, 3, 5, 8, 13, 20). Teams choose the scale that best suits their needs and helps facilitate effective task estimation and consensus-building.

What is the purpose of using Planning Poker in agile projects?

Planning Poker is used in agile projects to facilitate accurate and collaborative estimation of effort or relative size for user stories or backlog items. It helps teams gain a shared understanding of the work involved, promotes transparency, and aids in effective sprint planning and backlog prioritization.

How does Planning Poker promote team collaboration?

Planning Poker encourages team collaboration by creating a platform for open discussion and debate among team members during estimation. It allows everyone to share their perspectives, raise concerns, and provide insights, fostering a collaborative environment where collective knowledge is leveraged to arrive at more accurate estimations.

Are the Planning Poker numbers fixed or can they be customized?

The Planning Poker numbers can be customized based on the preferences and needs of the team or organization. While the Fibonacci sequence is commonly used, some teams might choose to modify the scale, introduce additional numbers, or even adopt a linear scale depending on their specific context and estimation requirements.

Can Planning Poker be used for estimating tasks other than user stories?

Yes, Planning Poker can be applied to estimate various types of tasks or backlog items, not just limited to user stories. It can be used to estimate technical tasks, bugs, epics, or any other work items that need to be estimated for planning purposes within an agile project.

How does Planning Poker address individual biases in estimation?

Planning Poker helps address individual biases by employing a collaborative approach. Since team members discuss and justify their estimations, it encourages them to consider multiple perspectives and challenge any personal biases or assumptions. Through consensus building and shared decision-making, the influence of individual biases is minimized, resulting in more accurate and unbiased estimations.

What is playing poker technique in agile?

Playing poker technique in agile refers to the practice of using Planning Poker, also known as Scrum poker, for estimating the effort or relative size of user stories and backlog items during sprint planning. It involves team members using a deck of cards with numbers to collaboratively assign values to these items based on discussion and consensus.

Is planning poker effective?

Planning Poker is generally considered effective for estimating work items in agile projects. It promotes collaboration, transparency, and helps in arriving at more accurate estimations, making it a valuable tool for sprint planning and backlog prioritization.

When should you play planning poker?

Planning Poker should be played during sprint planning or backlog refinement meetings when the Scrum team needs to estimate the effort required for user stories or backlog items. It is a best practice to use it before committing to work for a sprint.

What does the coffee cup mean in planning poker?

In Planning Poker, the coffee cup is a symbol that can serve two different purposes. First, it can be introduced to indicate that a team member needs a break or a moment to address concerns before continuing the estimation process. This practice ensures that everyone's input is considered, and team members have the opportunity to clarify any uncertainties. Secondly, in some teams, the coffee cup may also be used to signal a team member's uncertainty about which vote to choose, allowing them to express their hesitation during the estimation process. It's worth noting that in Scrum Jam, a similar concept may be represented using bananas 🍌 instead of a coffee cup. 🍵

What is the correct order of steps during planning poker?

The correct order of steps during Planning Poker typically involves the following: 1. A product backlog item is presented for estimation. 2. Team members vote anonymously by selecting and revealing their estimate cards simultaneously. 3. Discussion and clarification take place, with team members explaining their reasoning. 4. Team members re-estimate if necessary. 5. Repeat the process until a consensus is reached. This approach of anonymous voting followed by open discussion helps ensure that individual biases are minimized, and estimations are based on collective knowledge and consensus.

How many hours is 'x' story points?

The number of hours corresponding to a specific number of story points ('x') can vary depending on the team and their historical velocity. Story points are a relative measure of effort and don't directly translate to hours. The team should establish their own baseline for this conversion.

How many story points per 2-week sprint?

The number of story points a team can commit to in a 2-week sprint depends on their historical velocity and capacity. Teams should consider their past performance and available resources to determine a realistic commitment for a sprint.

How can I use ScrumJam's free Planning Poker online for collaborative estimation?

ScrumJam's online Planning Pokeris an easy-to-use agile project management technique. Here's how it works:

1. Create a room or join using a shared link.
2. Invite your team members.
3. Vote on task complexity.
4. Negotiate and agree on specific estimates.

This collaborative approach enhances team engagement and transparency, improving the accuracy of your sprint planning. You can try ScrumJam's free Planning Poker online tool to streamline your agile project management.