Search code examples
bug-tracking

Bug Fixing Time Allocation

We've been asked by a client to give us a time estimate on each and every bug we have.

Though we do have a set schedule for bug fixing and have allocated time for it, we don't have a time allocation on each of the bugs we have. Simply, we have prioritized our bugs and have ensured that Highest priority bugs will be fixed in the time allotted.

I'm not a fan of allocating time to bugs, simply because:

  1. It usually is inaccurate. It's very difficult to figure out how long it would take to fix.
  2. Waste of time.
  3. Affects code quality
  4. Creates more bugs in the long run (We may miss certain things in our attempt to complete it by the deadline).

How should we tackle this issue where we don't want to provide the number of hours per bug, but just a time frame as to what bugs will be fixed?

How do you allocate time to your bugs? Is it effective? Worth the time and effort?

Solution

  • The only answer I can give is to be extremely conservative. Guess how long it will take, and multiple your guess by four. Use that as your estimate. As you said, it's very difficult to figure out how long things will take to fix, and it's better to say it will take longer than it actually does than to be caught "breaking your deadline" because you weren't conservative enough.