Thanks for stopping by the Testing FTW! Blog. We are not trying to reinvent the wheel, the world or testing in general. Instead, we share the same belief in solution driven test management. In short, it's all about making quality problems go away, while getting most from your effort, while creating visibility and room for test in projects. The blog focusses on the solution to problems encountered as part of the software development cycle, aiming especially on the activities that relates to test.
One of my
peers asked me how I would calculate the cost of finding a bug the other day.
Reason for the quastion was that management was doing a RoI calculation on the
test effort in the project portfolio, and would like to know how much effort (read:
money) they would be spending to find a single bug.
Guesstimating based on a few metrics
knowing the price-tag for finding a defect is interesting, and my answer to the question
was something like this:
metrics from your test management tool, test plans, timelogging system or
like total number of test cases (TC) and defects fount, hours spend on TC
preparation and TC execution
spend on TC preparation + hours spend on TC execution)/ total test cases)*
Defect to test case ratio (Defects / TC)
159)/102)*(98/102) = 5,66 man hours / defect.
all the cost like test environment cost, training of testers, time spend on
defect management etc.