[rootedbox]

Sure there is. It's a ratio of inputs to outputs.. even in the example the inputs and outputs are measurable.

The only thing this article gets at is that engineers may not know how to calculate their own productivity; but it doesn't means it's not calculable.

[halfcat]

> It's a ratio of inputs to outputs.. even in the example the inputs and outputs are measurable.

But reality is never that clear cut. How’s the ratio look when:

- Peter goes to the park and the breakthrough doesn’t come?

- Or it comes 3 weeks later?

- Or he deletes 100 lines of code and introduces a new bug?

[pixl97]

>It's a ratio of inputs to outputs.. even in the example the inputs and outputs are measurable.

So more lines of code is better!

Um, we know this doesn't work that way as a good measure.

This is like comparing algorithms that do the same thing to algorithms that do different things. You're not going to get good valid comparisons. Metrics for one thing may not work at all for another.

[cjensen]

The output is measured with dollars, not lines of code. So are the inputs.

It's a perfectly cromulent measure so long as we understand the limitations of the measure. For example, trying to measure the productivity of a day or a sprint? That's silly. Measure the output of a team which does not produce an entire product? Won't work because you'd have to figure out how to apportion the productivity.