Title: At Trevor.io we recently released some fundamental changes to our platform, which, unsurprisingly, came with a handful of bugs.  This triggered a debate among the team: which bugs do we fix now?  Which do we fix later?  And when is later?  If we don&#x27;t fix them now, will we realistically ever fix them?<p>This led us to an interesting question: what if we just split <i>all</i> bugs into &quot;will fix&quot; and &quot;won&#x27;t fix&quot;, and then prioritise every &quot;will fix&quot; above all new features....always.  In other words: we commit to only ever adding new features when we&#x27;re bug free.<p>Has anybody tried this?  Can it work?
Upvote: