<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>planning poker on Agile Software Development</title>
    <link>https://agilesoftdev.com/tags/planning-poker/</link>
    <description>Recent content in planning poker on Agile Software Development</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 02 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://agilesoftdev.com/tags/planning-poker/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Planning Poker Works, But Not for the Reason Most Teams Think</title>
      <link>https://agilesoftdev.com/planning-poker-works-but-not-for-the-reason-most-teams-think/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://agilesoftdev.com/planning-poker-works-but-not-for-the-reason-most-teams-think/</guid>
      <description>Planning poker is an estimation technique in which team members simultaneously reveal their estimates for a story, then discuss discrepancies before converging on a number. The standard explanation for why it works is that simultaneous reveal prevents anchoring — no one&amp;rsquo;s estimate influences others before they have formed their own. This is true and not the main reason the technique is valuable.
The main reason planning poker works is that it makes disagreement visible.</description>
    </item>
    
  </channel>
</rss>
