# Get Better Results from Your Planning Poker Estimation | LinearB Blog

> The planning poker estimation technique is a strategy teams use to estimate the work of agile stories taken from group feedback.

_This is a markdown rendering of a live HTML page on linearb.io, generated for AI/LLM consumption — it is not a markdown-only site. To get the full HTML page instead, request this URL with an explicit `Accept: text/html` header (no wildcard, no markdown preference)._

[Blog](https://linearb.io/blog)

/

Get Better Results from Your Planning Poker Estimation

# Get Better Results from Your Planning Poker Estimation

![Photo of Keshav Malik](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/logo-mark-lg?_a=BAVMn6ID0)

By [Keshav Malik](https://linearb.io/blog/planning-poker-estimation#keshav-malik)

|

October 28, 2022

![planning_poker_estimation_962dbe5b61](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/planning_poker_estimation_962dbe5b61?_a=BAVMn6ID0)

If you’ve been anywhere near the software industry in the last decade, we know you’ve heard the word _Agile_. After all, many teams hopped on the Agile bandwagon, producing software to completion in short cycles. But planning a sprint isn’t that simple. The industry average for [planning accuracy in a sprint is below 50%](https://linearb.io/planning-accuracy/), meaning your teams aren’t planning out their sprints properly most of the time. So how do we fix this? Many teams have turned to a unique method called the Planning Poker Estimation technique.

But is this technique _really_ your best option for estimating projects? We don’t think so. 

## **Table of Contents**

* [What Is Planning Poker?](#what)
* [How the Planning Poker Estimation Technique Works](#how)
* [Planning Poker Alternatives](#planning)
* [The Limits of Estimation Techniques](#limits)
* [Get More from Your Planning Poker Estimation Technique](#get)

## **What Is Planning Poker?**

The planning poker estimation technique—aka scrum poker—is a gamified strategy that agile teams use to approximate the work of agile stories. Planning poker was first outlined and defined by James Grenning in 2002, but it would later be popularized in _Agile Estimating and Planning_ by Mike Cohn, whose company trademarked the term. 

Originally, planning poker was created to speed up the planning process, as the original [Wideband Delphi method](https://www.tutorialspoint.com/estimation%5Ftechniques/estimation%5Ftechniques%5Fwideband%5Fdelphi.htm) was too time-consuming. Instead, teams use playing cards to weigh in on the effort it would take for a particular user story. These estimations come from the entire group’s feedback and agreement, making the estimation activity seriously captivating. Wanna play?

![Pull quote saying "The planning poker estimation technique is a gamified strategy that agile teams use to approximate the work of agile stories".](https://assets.linearb.io/uploads/quote.png)

Shall we place some bets?

(Did you know that regular poker can also benefit software developers? Our COO, Dan Lines, sat down with Jeff Meyerson, and they discussed how playing poker can actually help you succeed in software development!) 

## **How Planning Poker Estimation Technique Works**

Let’s break the technique into two different parts to understand it easily.

### **1\. Initial Stage**

Before a poker-arranging meeting, the product owner or client either brings up a new feature, covers customer feedback, or does anything else that might warrant development time.

Then, each participant is handed a deck of cards, generally numbered 1-21 or in a Fibonacci sequence. These numbers can address a few things: how many story points they think it needs, how many days it might take, or any other metric that the team might use.

The planning poker cards are intentionally designed to start small and increment quickly, so participants are encouraged to come to an agreement. Assuming they have a card for each number from one to 50, the cycle would be agonizing.

The mediator (the product owner or scrum master) explains the case to the group. Members are free to ask more questions if they need more information. Once everyone’s heard the story, everyone shares their perspectives on it. 

Remote teams can run these meetings asynchronously by giving each estimator stories to weigh in on individually. This allows them each to take as much time as they need to fully flesh out their reasoning, and the mediator can use that to finalize a result.

![Image of the painting "Dogs Playing Poker".](https://assets.linearb.io/uploads/poker.jpg)

Do you think these pups reached a consensus yet?

### **2\. After-Discussion Stage**

After the discussion, each person will privately choose a card from the deck. Generally, the card will show an estimate of story points, but it can also represent the number of ideal days. Once everyone selects a card, everyone reveals their estimate.

If the universe is kind to you, team members show the same card. And this number turns into an accord. And you can then merrily move on to the next story.

But chances are, that won’t happen. Estimates fluctuate—like, a lot. So, the team will continue to have more dialogues on the story. People who choose higher or lower numbers will have to explain their points of view. They may even attempt to persuade others to follow suit.

Naturally, after several (sometimes frustrating) rounds, the numbers should start to look more uniform. And once everyone agrees on _one_ number, the game is over. The number will be the estimated time or duration for the project. You can go ahead and pop the confetti now! 

Does this feel reminiscent of your family game night? Yeah, it is. And just like your game nights with your dysfunctional bunch, you’re likely going to run into some problems with the planning poker estimation technique. 

[](https://linearb.io/planning-accuracy/)

We know that planning accuracy is hard. Learn more about [our six-step recipe for improvement](https://linearb.io/planning-accuracy/).

### **The Purpose of Planning Poker**

When Planning Poker first came into use, it was primarily designed to replace the existing method, called Wideband Delphi. That method was incredibly time-consuming and required the estimators to fill out forms to explain their reasoning behind their estimates. 

With Planning Poker, your team of estimators should be able to discuss each user story and get accurate estimates based on the number of story points you agreed upon. Since it’s intentionally a gamified technique, you challenge your development teams to be honest and accurate in setting goals in a sprint.

Planning accuracy is directly improved by using methods like this, and that can make a huge difference. In fact, these benchmarks allow you to create more detailed and accurate reports and _truly_ show what your teams are working on. And you can improve more than just that metric, especially when you start measuring other engineering metrics.

## **Planning Poker Alternatives**

If poker isn’t your game, your teams can still use other gamified techniques for sprint planning. Here are some other common alternatives:

* **Bucket System:** This game is similar to poker, but instead of passing around cards, you use buckets (or whatever equivalent you can find). Estimators discuss the number of story points required for the item and place it in a corresponding bucket. It’s a faster equivalent to planning poker but doesn’t allow for as many in-depth discussions.
* **T-Shirt Sizing**: This game involves—you guessed it—T-shirts, starting with extra small sizes and going up to XL. Basically, you assign items to these sizes to determine how difficult or tedious a task might be. This works much better for dealing with backlogged items but doesn’t provide you with any hard data or a concrete number of story points.
* **Dot Voting**: This method lets development teams cast votes using small stickers. You first lay out your assortment of issues, and your team places stickers to determine how important an item might be. The more stickers, the more work a task needs. But this game doesn’t give you any information about story points, it only shows you what’s most important for teams.

No matter which solution you end up using, you must remember that it won’t be a perfect method. These gamification techniques provide you with a loose estimation of your planning accuracy, but without hard data, that’s all it is—just an estimate.

## **The Limits of Estimation Techniques**

At the end of the day, these are all great techniques to _estimate_ your workloads, but what does that accomplish? You need hard data to show what your teams are getting done, and these games don’t provide that. 

The key to measuring planning efficiency is to get actual insights and data into how your team is performing, and how accurate their plans are. Without the insights, things will quickly go downhill. The planning estimations—which were great at first—end poorly, and cause delays you could’ve avoided. 

And once these delays start, they can ripple through the entire organization. A missed deadline can make a potential marketing campaign miss its mark, clients miss out on promised new features, and execs can’t commit to revenue targets. And now, instead of playing estimation poker, everyone’s playing a sad game of dominoes. 

Plus, none of these techniques can account for added work or unplanned additions during a sprint. Mike Gordon from Hippo gives us some great advice on this:

“…if you’re going to have ten story points, plan for seven of them and leave three of them unplanned. Because those three unplanned will always happen.”

[![Mike Gordon of Hippo](https://assets.linearb.io/uploads/LinearB-Youtube-Card_-Mike-Gordon-How-Hippo-Increased-Productivity-With-LinearB-1024x576.png)](https://linearb.io/blog/how-hippo-increased-productivity-with-linearb/)

Want to learn more about improving software development productivity? [Check out how our customer Hippo Insurance increased their productivity.](https://linearb.io/blog/how-hippo-increased-productivity-with-linearb/)

## **Get More from Your Planning Poker Estimation Technique**

Measuring your team’s planning accuracy is crucial to making sure your team can commit and hit their goals as needed. Even if you can get a good estimation down, that’s only part of the overall problem. And if you want to really take advantage of proper planning accuracy, LinearB’s [Project Delivery Tracker](https://linearb.io/project-delivery-tracker/) has it all baked right in for you.

Taking factors like unplanned work, backlogged items, and the overall release velocity of your teams can paint a much better picture of how often your teams are hitting their marks. The formula is simple: Better Planning Accuracy = Improved Delivery = More business value. 

[![planning accuracy over time](https://assets.linearb.io/uploads/Group-1796.png)](https://linearb.io/get-started/)

Using LinearB’s Project Delivery Tracker can help you visualize unplanned work your team is doing each sprint and improve your planning accuracy. [Book a demo today!](https://linearb.io/get-started/)

## Improve developer productivity with LinearB

Find us on

[](https://www.linkedin.com/company/linearb)
[](https://devinterrupted.substack.com/)

## Your next read

[![Cover image for Slack turns channels into the context engine for agentic AI](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_Post_Name_2400x1256_077524ba8b?_a=BAVMn6ID0)](https://linearb.io/blog/slack-jaime-delanghe-mcp-agent-context-channels)

Workflow

[Slack turns channels into the context engine for agentic AI](https://linearb.io/blog/slack-jaime-delanghe-mcp-agent-context-channels)

Slack Chief Product Officer Jaime DeLanghe breaks down how channels serve as the foundational context layer for human-agent collaboration. Learn why Slack is...

[![Cover image for Code generation is faster than ever, but shipping value isn't](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_AI_code_review_bottleneck_2400x1256_d73333ea46?_a=BAVMn6ID0)](https://linearb.io/blog/code-generation-faster-shipping-isnt)

Workflow

[Code generation is faster than ever, but shipping value isn't](https://linearb.io/blog/code-generation-faster-shipping-isnt)

Your team writes more code than ever, but less reaches production. AI moved the bottleneck to code review. Here's how to measure it and unblock your pipeline.&n...

[![Cover image for AI as a value multiplier: a human-centric approach to engineering leadership](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_Servant_Leadership_2400x1256_0cfd4e2a0c?_a=BAVMn6ID0)](https://linearb.io/blog/ai-as-value-multiplier-human-centric-leadership)

Workflow

[AI as a value multiplier: a human-centric approach to engineering leadership](https://linearb.io/blog/ai-as-value-multiplier-human-centric-leadership)

Super.com's Matt Culver explains why AI should be used as a value multiplier, not a cost-cutter, advocating for a human-centric approach to engineering...

## Structured data

_Machine-readable metadata (JSON-LD) embedded in the page for search/AI context — not content rendered on the page itself._

```json
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "LinearB",
  "url": "https://linearb.io",
  "logo": "https://assets.linearb.io/image/upload/v1715628027/logo-mark-lg.svg",
  "description": "LinearB is the engineering productivity platform that helps engineering leaders prove AI is improving throughput without sacrificing delivery confidence, flow efficiency, or developer experience.",
  "sameAs": [
    "https://www.linkedin.com/company/linearb"
  ],
  "award": [
    {
      "@type": "Award",
      "name": "LinearB is a Leader in the 2026 Gartner® Magic Quadrant™ for Developer Productivity Insight Platforms",
      "dateAwarded": "2026",
      "awardedBy": {
        "@type": "Organization",
        "name": "Gartner®"
      }
    },
    {
      "@type": "Award",
      "name": "Great Place to Work Certification",
      "dateAwarded": "2025-2027",
      "awardedBy": {
        "@type": "Organization",
        "name": "Great Place to Work"
      }
    },
    {
      "@type": "Award",
      "name": "America's Best Startup Employers 2025",
      "dateAwarded": "2025",
      "awardedBy": {
        "@type": "Organization",
        "name": "Forbes Magazine"
      }
    }
  ],
  "hasCertification": [
    {
      "@type": "Certification",
      "name": "SOC 1 Type 2"
    },
    {
      "@type": "Certification",
      "name": "SOC 2 Type 2"
    },
    {
      "@type": "Certification",
      "name": "GDPR Compliance certification"
    },
    {
      "@type": "Certification",
      "name": "ISO 27001"
    }
  ]
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Get Better Results from Your Planning Poker Estimation",
  "url": "https://linearb.io/blog/planning-poker-estimation",
  "author": {
    "@type": "Person",
    "name": "Keshav Malik"
  },
  "datePublished": "2022-10-28T08:00:00.000Z",
  "dateModified": "2022-10-28T08:00:00.000Z",
  "image": "https://assets.linearb.io/image/upload/v1720000000/planning_poker_estimation_962dbe5b61.png",
  "publisher": {
    "@type": "Organization",
    "name": "LinearB",
    "logo": "https://assets.linearb.io/image/upload/v1777485755/linearb-logo-2026.png"
  },
  "description": "The planning poker estimation technique is a strategy teams use to estimate the work of agile stories taken from group feedback. \n"
}
```

## More on linearb.io

### Top navigation

- [Book a Demo](https://linearb.io/book-a-demo)
- [AI Code Reviews — Catch security risks, bugs, and spec mismatches](https://linearb.io/platform/ai-code-reviews)
- [AI & Productivity Insights — See how AI tools affect cycle time and delivery speed](https://linearb.io/platform/ai-developer-productivity-insights)
- [Measure AI Impact — Track AI adoption and tie it to delivery outcomes](https://linearb.io/use-case/measure-ai-impact)
- [MCP Server — Chat with your data to spot patterns and boost output](https://linearb.io/platform/mcp-server)
- [Resource Allocation — Cost initiatives and shape your investment strategy](https://linearb.io/platform/resource-allocation)
- [Cost Capitalization — Capitalize engineering costs with audit-ready reports](https://linearb.io/platform/cost-capitalization)
- [Dev Team Management — Set targets and tie throughput to business outcomes](https://linearb.io/platform/goals-and-reporting)
- [DevOps Workflow Automation — Policy-based PR routing, approvals, and tests](https://linearb.io/platform/ai-workflow-governance)
- [AI Powered Support — Unify AI and human code delivery in one clear view](https://linearb.io/use-case/ai-powered-support)
- [Optimization — Surface friction with feedback and MCP insights](https://linearb.io/platform/developer-experience)
- [Reporting — Spot what's working and what needs attention](https://linearb.io/use-case/measuring-developer-experience)
- [Surveys — Turn developer feedback into actionable signals](https://linearb.io/platform/developer-surveys)
- [Platform overview](https://linearb.io/platform/overview)
- [Register now](https://linearb.io/event/engineering-productivity-gap)
- [Customers](https://linearb.io/customers)
- [Pricing](https://linearb.io/pricing)
- [Why choose LinearB — Explore your data. Measure performance. Act to improve it.](https://linearb.io/why-linearb)
- [APEX framework — The operating model for AI-era engineering teams](https://linearb.io/resources/apex-framework)
- [Anti-FAQ — The questions other vendors won't answer](https://linearb.io/why-linearb/anti-faq)
- [Security — Enterprise-grade compliance and zero code access](https://linearb.io/security)
- [Build vs. buy — The hidden cost of building it yourself](https://linearb.io/resources/build-vs-buy)
- [Dev Interrupted Podcast — Conversations with engineering leaders](https://linearb.io/dev-interrupted/podcasts)
- [Reports & Guides — Deep dives on productivity and delivery](https://linearb.io/resources)
- [Webinars — Expert sessions on productivity and AI](https://linearb.io/resources?category=workshops)
- [Metrics Benchmarks — See how your engineering org stacks up](https://linearb.io/resources/software-engineering-benchmarks-report)
- [Blog — Product updates and practical insights](https://linearb.io/blog)
- [Help Center — Documentation, setup, and support](https://linearb.helpdocs.io)
- [API Docs](https://docs.linearb.io/api-overview)
- [Status](https://www.linearbstatus.com/)
- [Integrations](https://linearb.io/integrations)
- [LinearB is a Leader in the 2026 Gartner® Magic Quadrant™ for Developer Productivity Insight Platforms](https://linearb.io/resources/gartner-magic-quadrant-dpi-platforms-2026)
- [Sign in](https://app.linearb.io/login)
- [Enterprise](https://linearb.io/solutions/enterprise)
- [Contact](https://linearb.io/contact-us)
- [About us](https://linearb.io/about-us)
- [Careers](https://linearb.io/careers)
- [Service agreement](https://linearb.io/services-agreement)
- [Privacy policy](https://linearb.io/privacy-policy)
- [DPA](https://linearb.io/data-processing-agreement)
- [Security FAQ](https://linearb.io/security-faq)
- [Substack](https://devinterrupted.substack.com/)

### Footer

_Additional links from the site footer, not repeated from the top navigation above._

- [GitHub](https://github.com/linear-b)
- [LinkedIn](https://www.linkedin.com/company/linearb)
- [Twitter](https://twitter.com/LinearB_Inc)