Code Churn: post-release defect elimination
Among numerous metrics on code evaluation (like CRAP index) in product lifecycle, code churn seems to be the one to look for while dealing with post-release and legacy code elimination. Code churn helps you to evaluate file changes across builds. Code churn is a good predictor of post-release defects. Thus, it’s a warning sign if you approach a deadline while your code churn increases. That’s a sign that the code gets more and more volatile the closer you get to your deadline. You want the opposite. You want to stabilise more and more code the closer you get to delivery. > > Codescene Code Churn features One of the features of code churn - is bottleneck finding across developers and tasks. Low commit rates per author can signal the management, that there’s some sort of problem going on: ...