[sirobg]

I worked in a company who measured productivity by attributing a score based on the Fibonacci scale. But they were doing this when the feature was done.

By doing that, it was fairly easy to give a relevant score to each feature.

Engineering team was doing this to measure solely engineering productivity, but product team could do this as well to measure added value to the company.

By tracking the start/end date as well for each feature, you can then measure productivity at any time scale you want.

[flavianh]

That’s very interesting, what is the score based on?

[sirobg]

It was supposed to represent "how big" the feature was.

As it's subjective and vague, the score was suggested by the engineer in charge of the feature and then (rapidly) approved by the team during daily meetings.

But I guess this principle could be applied with a score representing whatever you want to track, and however you want to track it.