As a metric of software quality, we calculated the ratio in the Title.
The value of this KPI should have the following meaning:
- 0 (0%) = no work on bug, this means that all the time spent on the project was used for new features, great!
- 1 (100%) = working only on bug, this could be a legacy project, where there are no new features so all the time spent on that project is about bug fixing&testing;
- 0.5 (50%) = half of the time is spent on bug fixing&testing, this could be a problem in a normal project.
So the question is: in a normal project (not legacy) what could be a healty value of that KPI?
Someone told me 33% but I cannot find any literature about that value.