LOC was used extensively in costing models with waterfall development, and even some with iterative dev. But things have changed some. One thing I still use i

LOC was used extensively in costing models with waterfall development, and even some with iterative dev. But things have changed some. One thing I still use it for is monitoring features to maintainability. In other words, in established products/projects I will monitor my teams LOC checked in and I look for it to stay as small as possible or to decrease with revisions. Obviously this doesn't always happen, but I would rather reward the guy who removes 50 LOC versus the guy that adds 200, assuming they both got the same job done and features were delivered. I feel that LOC should never be used outside of the development team. i.e. No non-technical business mgr should ever see the metric as it is too easy to misunderstand or abuse. Also, LOC as I use it for established teams is almost totally useless in startups as the amount of code is usually pretty rapidly changing and expanding. Thus making LOC deceiving and misleading in my opinion.