The closer code comes to shipping, the more tech debt should be reported in a targeted manner.
Today a new release was cut along with new technical debt that was branched with it.
Shipped code is a natural time to take stock of recent technical debt. Why? Because debt should be minimized and shipped code with debt should also be minimized.
By reporting debt to the class, metric and developer level the debt was made actionable and visible. Such tech debt reports were always available during the sprint but often take back burner to seemingly more pressing development, But the targeted reporting by leads and reviewers to management started 9 days earlier. At that point 33 developers had debt. By the time of the branch, the targeted reporting had nearly halved that to 18.