In a recent CTO/CIO Perspectives column, ‘IT extremism strikes again: the odd resistance to bug tracking’. Peter Kretzman shared some justified frustration with a subset of young software developers whose ‘out of the box’ thinking includes a resistance to systematic bug tracking.
In his funny, opinionated and insightful article Kretzman highlights the dangers of assuming that all bugs will be fixed as they occur – especially in major software systems. He points out that the lack of any tracking mechanism allows a team to claim bug-freedom without fear of contradiction, and the errors of maintaining a state of denial. He concludes: ‘Bottom line: when you hear people dismissing the need for various long-standing, solidly understood processes in the development of software, it’s appropriate to be tremendously skeptical.’
Kretzman links to relevant blog posts from issue tracking industry experts, including an Issuetrak item first published in 2014. Since readers continue to comment on the usefulness and relevance of our article, we thought it worth highlighting the article again: “Top 10 Reasons Why Your Organization Needs Issue Tracking Software”. Meanwhile, below is a quick summary of the key points discussed:
- Important issues get lost.
- Employees and managers waste too much time trying to find out what’s going on.
- Customers don’t know if their issue has been resolved.
- Employees don’t realize they’ve been assigned an issue.
- Management can’t tell who is working on what.
- Some employees have too many issues to resolve while others have few.
- Getting reports takes too long.
- You can’t leverage problems you’ve already solved.
- Managers don’t know the cost of resolving specific problems
- You could face legal penalties for not having a record of all activities surrounding problems and projects
If you’re faced with a situation where an out-of-the-box thinker wants to fly blind on the issue of bug-tracking, this will help!