Skip to main content
11 events
when toggle format what by license comment
Feb 8, 2017 at 13:41 comment added Bart van Ingen Schenau @greenkey: I can reach the 0 time metric by simply ignoring all bugs that come in. In that way, no time spent on fixing bugs does not indicate that there are none. Just that nobody worked on them.
Feb 8, 2017 at 12:53 comment added Gürkan Çetin Exciting question. The answer also depends on the lifecycle phase and philosophy of the project. Are new features added incrementally (as in agile) or is it a waterfall of requirements? Let me picture it this way: the first days, the ratio will be 0.0, no bugs; and when V&V starts, the ratio starts to rise, maybe up to 1.0, and then the ratio stays there as long as there are no new higher level change or feature requests.
Feb 7, 2017 at 9:48 comment added Nathan I think using this as a KPI would be counter productive. In order to get in a position where bugs and bad code aren't holding you back you have to take them on directly. As a KPI this may point out a problem, but it also disincentivises solving it.
Feb 7, 2017 at 8:46 comment added greenkey @CodeGnome why you think it's flawed? I know it's almost impossible, it's only an example.
Feb 7, 2017 at 8:46 comment added greenkey @Venture2099 both, but mainly pre-release ones.
Feb 7, 2017 at 5:50 answer added Luc Pavot timeline score: 1
Feb 7, 2017 at 3:28 comment added Todd A. Jacobs Your metric assumes time not spent on bugs means there are no bugs. This is flawed on its face.
Feb 6, 2017 at 21:11 review Close votes
Feb 7, 2017 at 9:04
Feb 6, 2017 at 18:48 comment added Venture2099 Context dependent. Also depends on automated testing and BDD. Do you mean escaped defects to Production or do you mean pre-release defects?
Feb 6, 2017 at 18:23 review First posts
Feb 6, 2017 at 20:51
Feb 6, 2017 at 18:18 history asked greenkey CC BY-SA 3.0