Reasons not to build your own bug tracking system,
Several times now I’ve been faced with plans from a team that wants to build their own bug tracking system – Not as a product, but as an internal tool.
The arguments I’ve heard in favous are usually along the lines of :
- Wanting to ‘eat our own dog food’ in terms of some internally built web framework
- Needing some highly specialised report, or the ability to tweak some feature in some allegedly unique way
- Believing that it isn’t difficult to build a bug tracking system
What arguments might you use to support buying an existing bug tracking system? In particular, what features sound easy but turn out hard to implement, or are difficult and important but often overlooked?
First, look at these metrics:
Trac: 44 KLoC, 10 Person Years, $577,003 Bugzilla: 54 KLoC, 13 Person Years, $714,437 Redmine: 171 KLoC, 44 Person Years, $2,400,723 Mantis: 182 KLoC, 47 Person Years, $2,562,978
What do we learn from these numbers? We learn that building Yet Another Bug Tracker is a great way to waste resources!
So here are my reasons to build your own internal bug tracking system:
- You need to neutralize all the bozocoders for a decade or two.
- You need to flush some money to avoid budget reduction next year.
That’s the answer Reasons not to build your own bug tracking system, Hope this helps those looking for an answer. Then we suggest to do a search for the next question and find the answer only on our site.
The answers provided above are only to be used to guide the learning process. The questions above are open-ended questions, meaning that many answers are not fixed as above. I hope this article can be useful, Thank you