<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>product-management on Matt Sencenbaugh</title>
    <link>https://mattsencenbaugh.com/categories/product-management/</link>
    <description>Recent content in product-management on Matt Sencenbaugh</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Fri, 15 Mar 2013 00:00:00 +0000</lastBuildDate><atom:link href="https://mattsencenbaugh.com/categories/product-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The &#34;Priority Queue&#34; Development Process</title>
      <link>https://mattsencenbaugh.com/the-priority-queue-development-process/</link>
      <pubDate>Fri, 15 Mar 2013 00:00:00 +0000</pubDate>
      
      <guid>https://mattsencenbaugh.com/the-priority-queue-development-process/</guid>
      <description>TLDR - Programmers are bad at giving time estimates so we shouldn&amp;rsquo;t ask them to. To be more efficient an organization should experiment with a process that simply places 3 items in each developers &amp;lsquo;PQueue&amp;rsquo; and let them finish it.
PQueue My tech teammate was up from Austin this week and suggested that our dev team try out a process similar to what his old team used at Demand Media. The basic idea is that instead of doing agile or waterfall, Demand Media simply assigned each developer a queue of the highest priority tasks they could be working on at that moment (with a cap of 3).</description>
    </item>
    
  </channel>
</rss>
