10 years and still Cannot Measure Productivity

This content is syndicated from Martin Fowler by Martin Fowler. To view the original post in full, click here.

One of the great frustrations of the software industry is that we don’t have properly built studies to figure out whether development tools and techniques such as object-oriented programming, test-driven development, or even high-level languages are good for us. Regularly we see improperly built studies that do so - often these are done poorly because they rely on a bogus measure of productivity (such as Lines of Code per staff day). 10 years ago today, my frustration led me to publish my bliki post CannotMeasureProductivity. I think this post is sadly just as sound today as it was a decade ago.

Leave a Reply

What is 2 + 1 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

There are 101 ways to approach anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”