Reasons not to build your own bug tracking system -
several times i've been faced plans team wants build own bug tracking system - not product, internal tool.
the arguments i've heard in favous along lines of :
- wanting 'eat our own dog food' in terms of internally built web framework
- needing highly specialised report, or ability tweak feature in allegedly unique way
- believing isn't difficult build bug tracking system
what arguments might use support buying existing bug tracking system? in particular, features sound easy turn out hard implement, or difficult , important overlooked?
first, @ these ohloh 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 learn these numbers? learn building yet bug tracker great way waste resources!
so here reasons build own internal bug tracking system:
- you need neutralize bozocoders decade or two.
- you need flush money avoid budget reduction next year.
otherwise don't.
Comments
Post a Comment