Elementool’s Bug Tracking Saves Hundreds of Hours a Month in
Software Development Time
Excel\E-mail\In-house Solution Elementool Bug Tracking
information regarding issues
Developers fixing bugs
according to their priority
Instant project status report
Monthly development time saved for a team of 10 developers: 340hrs - $10200 worth
Accurate communication is the key to the success of the bug tracking process. This
communication takes the form of timely information flow between customers, QA and
Development. Reducing the time spent on tasks that communicate bug information saves money.
Let’s explore the tasks completed daily by personnel in software development throughout the
development process. We’ll compare the time and money spent on the tasks when they have Bug
Tracking and when they don’t. The average time spent on a task and the costs per hour are
based on actual experience at Elementool Inc.
To start, with Elementool’s Bug Tracking, the user logs in to the account and immediately sees all
relevant information. This gives a snapshot or overview of the bugs currently in the system. They
can see exactly how many issues are assigned to them. The issues are sorted by status, severity,
priority or any other criteria the user might choose.
This type of report takes about five minutes to create using in-house software or Excel. Done
once an hour that is 40 minutes a day of saved time. That is 15 hours per month or $450 worth of
a programmer’s time.
Another near constant demand for the QA or development person is the need to attach files to
various issues reported to the system. Then, when a user works on fixing a bug, they have
access to the files related to the bug. For example, issues related to the UI could be pictured in a
screen shot an