<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Anthony Palumbi</title>
    <description/>
    <link>https://speakerdeck.com/apalumbi</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/apalumbi.rss"/>
    <lastBuildDate>2018-06-29 11:32:54 -0400</lastBuildDate>
    <item>
      <title>What's the point?  Everything is an "8".  Introducing your team to #NoEstimates</title>
      <description>We have all been there. It’s Monday, 3rd hour of a 7 hour planning meeting. So far, your team has estimated 2 stories and it’s a good chance that you are going to be delaying the start of the sprint so that you can finish this meeting tomorrow. Your product owner is driving out minute details of the work so that the team can agree on the same number of points. In your head you are saying "What's the point?" Finally, the devs agree that this story is a 5 pointer...then all of a sudden your tester wants to add 3 more points. So...it's an 8...again. Like the last story that we spent two hours on.

The main premise of the no estimates movement is centered on the idea that spending time getting "accurate" estimates is mostly wasted when compared to spending that same time building the next most valuable feature for your product.

In truth, no estimates doesn’t actually mean no estimates. This talk will focus on strategies that you can apply to your team's next planning meeting that will help you spend less time going back and forth on a made up number and more time doing valuable work. We will cover some of the traps of the standard agile estimation model and what motivates organizations to want to spend time estimating.</description>
      <media:content url="https://files.speakerdeck.com/presentations/eedcfdf9b8334bcab85c5ddac9d74c7c/preview_slide_0.jpg?10320642" type="image/jpeg" medium="image"/>
      <content:encoded>We have all been there. It’s Monday, 3rd hour of a 7 hour planning meeting. So far, your team has estimated 2 stories and it’s a good chance that you are going to be delaying the start of the sprint so that you can finish this meeting tomorrow. Your product owner is driving out minute details of the work so that the team can agree on the same number of points. In your head you are saying "What's the point?" Finally, the devs agree that this story is a 5 pointer...then all of a sudden your tester wants to add 3 more points. So...it's an 8...again. Like the last story that we spent two hours on.

The main premise of the no estimates movement is centered on the idea that spending time getting "accurate" estimates is mostly wasted when compared to spending that same time building the next most valuable feature for your product.

In truth, no estimates doesn’t actually mean no estimates. This talk will focus on strategies that you can apply to your team's next planning meeting that will help you spend less time going back and forth on a made up number and more time doing valuable work. We will cover some of the traps of the standard agile estimation model and what motivates organizations to want to spend time estimating.</content:encoded>
      <pubDate>Fri, 29 Jun 2018 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/apalumbi/whats-the-point-everything-is-an-8-introducing-your-team-to-number-noestimates</link>
      <guid>https://speakerdeck.com/apalumbi/whats-the-point-everything-is-an-8-introducing-your-team-to-number-noestimates</guid>
    </item>
  </channel>
</rss>
