4 ms·
Backlogs should be a bounded queue, not unbounded. You need something that's longer than 5 people's collective short term memory. But as soon as it has items th
by quantified 4y ago
Backlogs should be a bounded queue, not unbounded. You need something that's longer than 5 people's collective short term memory. But as soon as it has items that are "too old" * "too minor", there's a great chance they start becoming obsoleted, recognized as worthless, etc.
- JohnFen 4y agoTough to do, though, because there can be genuinely important stuff in the backlog that shouldn't be forgotten, but for various reasons won't be tackled anytime in even the medium term future.
- flappyeagle 4y agoI mean, most ticket systems let you filter by date created or updated... seems like you can ignore stuff that's older than x months.
- quantified 4y agoNot always. You get into an X month crunch because your salespeople sold far far ahead, some old things are still relevant. But date's a good proxy. The older it is, the more likely a newer ticket was created for it as well to be sure
- 9dev 4y agoThe neat thing about those items is that you’ll never get to them anyway. We sort our backlog by priority constantly, and all of the junk, old issues, or irrelevant bugs simply get shifted to the bottom over time, with more important stuff sorting itself up. Nevertheless, if I come across something I’ve documented before, I don’t need to file the same issue over and over again; if multiple customers request the same stupid thing over time, you’ll have a track record and maybe notice there’s a need for something; and finally, a long backlog gives lots of opportunities to onboard new people with long-standing, but minor issues.