Scrum Teams should normalize their estimates (by using the same reference
scale), so that management can compare team velocities and use them as a
coordinated productivity measure.
[A] True
[B] False
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
[B] False When normalization implies ‘commoditization’ of story points, it can skew people's ideas of what constitutes value. The point of departure is that the measure of productivity in Scrum should always be the delivery of working increments. Therefore, such normalization is considered a bad ideRead more
[B] False
When normalization implies ‘commoditization’ of story points, it can skew people’s ideas of what constitutes value. The point of departure is that the measure of productivity in Scrum should always be the delivery of working increments. Therefore, such normalization is considered a bad idea in principle – and so answer B is correct. However, although story points estimates should not by used by management as a productivity measure, the normalization of estimates can be useful in practice, especially when multiple teams are working on the same product backlog.
See less