Code churn measures quantify how much change is occurring in your project.
Code churn measures quantify how much change is occurring in your project. In general, high levels of churn indicate project instability. You should expect high rates of churn at the start of a product cycle or after the team has implemented many changes. Toward the end of an iteration or before a release, you should expect the level of churn to decrease, which indicates that your project is more stable.
See http://msdn.microsoft.com/en-us/library/ms244661%28v=vs.110%29.aspx