[mym1990]

Its partly this, but hardly any developers I know were writing code for 8 hours a day. 4 on a good day and the rest was meetings or other auxiliary activities. From what I have gathered, companies have no idea how to measure the productivity gains yet.

[OneMorePerson]

When you look into the edge cases developer productivity is really tough to understand. It's easy as the engineer yourself to see your own productivity as easy to understand, but if you are ever in the position of trying to assess someone's productivity that you don't work with day to day, its really difficult. There are people who are able to achieve millions in yearly savings with like 10 lines of code updated per year, perf debugging types. I'd never believe that up front if I hadn't seen it after the fact.

[mym1990]

Its interesting to me that over the last 10 years of working in agile teams, not one team has analyzed burn rates to see if we are doing better/worse over time. Its like every sprint is a clean slate and no one actually gets better at their job...