Rapid Defect Resolution:
Immediate and Measurable ROI
Industry sources like IDC estimate that 37% percent of a developer’s work week (approximately15 hours) is devoted to dealing with software defects. Other sources put that number as high as 50%. Complex deployment environments, time to market pressure and rapidly evolving business requirements contribute to this drain on resources and time.
Software defects can show up in any point of the development life cycle: design and unit test, system integration test, user acceptance test, pre-production—and the Quality Assurance organization is the center point for identifying and clearing the issues. When the defect management process is examined in more detail from the perspective of development and QA, it is clear why it is so expensive in terms of time and effort:
| Step | Estimated Proportion of Time Spent | Challenges |
1. QA Finds Defect, Logs and Documents |
20% |
|
2. Developer Recreates Defect |
20% |
|
3. Developer Isolates Root Cause |
30% |
|
4. Developer Fixes, Verifies and Submits Update |
30% |
|
As an example, assuming ReplayDIRECTOR will save 50% of a developer’s time spent on fixing bugs, that is 7.5 hours per week or close to 400 hours per year. With a conservative $50 per hour for cost, this is close to $20,000 per year. The time saved in the QA organization avoiding the laborious and error prone defect documentation process can add significantly more in terms of total savings.
With these conservative estimates, it takes less than a month to payback an investment in ReplayDIRECTOR.
It’s easy to use your organization’s defect rate and cost factors to determine the savings that ReplayDIRECTOR will deliver. Check out our ROI calculator that will facilitate that calculation (http://www.replaysolutions.com/resources/roi-calculator).

