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%

  • Collecting enough information to fully communicate the issue
  • Up to 24 hour delays between QA and Dev deals in geographically dispersed organizations

2. Developer Recreates Defect

20%

  • Lack of access to QA test environments
  • Difficulty in recreating user load, network and database conditions

3. Developer Isolates Root Cause

30%

  • Insufficient documentation
  • “Works on my machine”

4. Developer Fixes, Verifies and Submits Update

30%

  • Uncertainty in terms of true root cause and environmental factors
  • Multiple attempts at resolution

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).
Quotes:
Play back the recording in the regular Eclipse Java debugger as often as you like to figure out the problem. - Stephen Smith - VP R&D - Sage Software
Play back the recording in the regular Eclipse Java debugger as often as you like to figure out the problem. - Stephen Smith - VP R&D - Sage Software
The problem was un-reproducible. Without Replay, we wouldnt have had a chance at fixing it. - John W. - Sr. Software Engineer
The problem was un-reproducible. Without Replay, we wouldnt have had a chance at fixing it. - John W. - Sr. Software Engineer
Take the ReplayDIRECTOR 3 Minute Tour:
Solutions:
ReplayDIRECTOR Developer Edition
ReplayDIRECTOR Developer Edition