Link Type of Work, Churn/New Code, Code Hotspots
Problem to solve
Right now we look at the type of work, i.e. tech debt
, bugs
/ new code, churn / code hotspots in isolation. All of these graphs provide valuable insight in terms of type of work, quality and velocity, but they say nothing about the cause.
- Do we have a lot of churn, because of changing requirements - what can we do to fix this?
- Do we have code hotspots, where the majority of our bugs are concentrated and yet no refactoring in that part of the codebase - what can we do to fix this?
- Some of our MRs take a very long time to merge, is that because they are touching on particular code hotspots?
Intended users
EMs, Tech Leadership
Further details
Proposal
UX research required
Permissions and Security
Documentation
Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Links / references
Edited by Virjinia Alexieva