The August 1, 2007 edition of SD Times has an article on bug tracking systems. I’ve long advocated that they should be used for any and every bit of corporate knowledge regarding one’s product(s). It should be no surprise then that I picked out these two nuggets from it.

  • Defect tracking is less about listing bugs than fostering communication among everyone, from developers to salespeople to customers; defect-tracking tools are indispensable to efforts to reproduce bugs and perform regression testing; and such tools should always be flexible enough to adapt to the developers using them, not the other way around.
  • This approach, he continued, is simply about prioritizing to-do lists, not forgetting anything important, and giving everyone on the team a reasonable idea when assigned tasks and projects are likely to be completed.