Delete bugs older than a week

Debugging issues usually happen in a production environment. The majority of the rest of the bugs are already live. They have been in your bug tracking system/on your wall for a while. Delete those. If the bug is still valid, it will get reported again.

Don’t waste time going through lists of obsolete bugs. If you’re using a bug tracking system, find all bugs created before releasing them and delete them. Waiting too long to resolve a bug increase the complexity of understanding the problem and having a smooth debugging session.

If you wait two months to address a reported bug, you will have forgotten the code and need to relearn the issue, context, and implementation. Instead of focusing on old bugs without real-time context for debugging, removing bugs that are older than a week is more manageable.

By keeping a bug-free codebase, you can ship your product to customers, with high quality, at all times. When there are no visible bugs in a system, every new feature adds value to customers.

If you need to get a feature in for a customer demo, you can put it in place and ship it without fixing any accumulated bugs. No bugs mean increased agility which improves the ability to produce better estimates.

The accumulation of bugs leads to mistrust from customers. Each bug may not seem like a big deal, but the proliferation of many bugs erodes the trust customers put in the company.