A project manager at our company recently supplied the team with metrics for two past projects that are wildly different from one another. Based on these metrics, the project manager would like to create a baseline for future projects however, I'm finding it difficult to grasp how that would be possible because future projects could have varying degrees of difficulty, resource availability, and other issues.
Sprint 3.1 to 3.6 data - 6 sprints - 12 weeks Total Design Hours 41 Total Development Hours 250 Number of PBIs 46 Number of bugs 45 Estimate hours fixing bugs 90 Estimated hours new development 160 Defect injection rate (number of hours fixing bugs / number of hours developing functions) 0.56 Average team development hours completed per sprint 42
Sprint 2.3 to 3.5 data - 7 sprints - 14 weeks Total Design hours 12 Total Development Hours 124 Number of PBIs 20 Number of bugs 13 Estimate hours fixing bugs 26 Estimated hours new development 98 Defect injection rate (number of hours fixing bugs / number of hours developing functions) 0.27 Average team development hours completed per sprint 18
The primary concern here seems to be that the
Average team development hours compeleted per sprint is around 40-50% of actual capacity and that the
Defect injection rate is too high for the harder project. But these are the two fields selected to the baseline for future projects. But what does this mean exactly? How can you arbitrarily just select the metrics from one of these projects and apply them to a future project? After looking at this question What is the best way to develop a project baseline? it looks like we might be conflating different ideas.