<story><title>Pivotal Tracker will shut down</title><url>https://www.pivotaltracker.com/blog/2024-09-18-end-of-life</url></story><parent_chain><item><author>aantix</author><text>The thing that I always liked about Pivotal is that it was visibly obvious that there was only one queue.&lt;p&gt;It forced everyone to ruthlessly prioritize and make the hard decisions.&lt;p&gt;In this moment, do you want me working on this bug, or this new feature?  You have to decide - you get one or the other.&lt;p&gt;It avoided the &amp;quot;Everything is a high priority&amp;quot; dilemma.</text></item></parent_chain><comment><author>teeray</author><text>I also loved that it was adamant about having specific, defined states with no customization. The issue is todo, in progress, done, delivered, accepted… that’s it. Custom issue states are a special kind of hell in JIRA.</text></comment>
<story><title>Pivotal Tracker will shut down</title><url>https://www.pivotaltracker.com/blog/2024-09-18-end-of-life</url></story><parent_chain><item><author>aantix</author><text>The thing that I always liked about Pivotal is that it was visibly obvious that there was only one queue.&lt;p&gt;It forced everyone to ruthlessly prioritize and make the hard decisions.&lt;p&gt;In this moment, do you want me working on this bug, or this new feature?  You have to decide - you get one or the other.&lt;p&gt;It avoided the &amp;quot;Everything is a high priority&amp;quot; dilemma.</text></item></parent_chain><comment><author>cpeterso</author><text>An alternative to one big queue is a separate queue for each client (external customers, internal teams, the dev team&amp;#x27;s own tech debt, etc) as described in &amp;quot;JIT selection from independent streams: An alternative to the “big backlog” of work&amp;quot;:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;longform.asmartbear.com&amp;#x2F;jit-backlogs&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;longform.asmartbear.com&amp;#x2F;jit-backlogs&amp;#x2F;&lt;/a&gt;&lt;p&gt;Each client manages their queue order, so the dev team just needs to focus on the head of each queue. (Of course, the dev team should also work with clients to clarify the requirements for the next few tasks in their queues so the head task will be shovel-ready). The dev team can then choose which queue heads to prioritize and maintain a balance, such as always have one tech debt task and X bug fix tasks in progress in addition to client work.</text></comment>