Secret ingredients to quality software


Do you constantly add to the backlog?

Last updated by Stephen Carter on 17 Jan 2017 06:12 am (over 4 years ago) See History

In the course of work everyone encounters bugs or problems. They can be dealt with by either:

1. Pretend you didn't see the problem
2. Fixing it straight away
3. Add the issue to the backlog so someone else can fix it

The best solution is to use a combination of 2 and 3.

  • If it will take less 15 mins to fix, do it straight away.
  • If it will take more time, add the problem to the product backlog and email a link to the appropriate person (even if it’s a third party product).

This approach raises the question of priorities. If you hit too many hurdles you continually get diverted from the main task: for example when fixing the Client form you encounter a problem with the Client Contact form which breaks the Products form etc. (This can be described as the "Tree Approach" as opposed to the "Straight through to the Goal approach".)

You need to try to balance short term productivity with long term improvements. My view is that it is better to get 2 things done at 100% than get 4 things done at 75%! At a minimum, always add the issue to the backlog.

Adam CoganAdam Cogan
Eric PhanEric Phan

We open source. This page is on GitHub