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.
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.