Secret ingredients to quality software


Management - Do you fix bugs first?

Last updated by Tiago Araújo [SSW] on 16 Apr 2021 12:55 am (2 months ago) See History

This rule has been important for a long time: Fix bugs before adding functionality.

  • Bugs get more expensive as they get older
  • Bugs become more complex the longer you wait to fix them
  • You have better access to the developer who created it who will be able to fix it faster

Failing to follow this rule encourages developers and creators to focus on new 'interesting' functionality which is exactly what you don't want... You must be strong in the face of pressures from project plan scheduling!

Note: The principle of this bug rule can apply to more than just developers.

Let's suppose you work in Marketing and have a problem with a hypothetical report. You should fix that issue first, before adding new information to the report.

Adam CoganAdam Cogan

We open source. This page is on GitHub