StopWorryingAndLoveMetrics

From SPA Wiki

Points, issues and questions raised during the workshop

• some metrics should not be exposed

• eg, exposing the mechanics of "load factor" leads to a world of pain

• don't measure/report everything all the time, wait for a trigger (usually the perception of a problem)

• measure the number of "emotional highs and lows" during an iteration

• most of the quantitiies presented are internal to the team, there's a lack of a way to measure things extenal to the team, particularly productivity

• do metrics provide a way to compare one XP team with another (mainly for productivity purposes)

• probablhy not

• measure the customer (useful, but they don't like it)

• measurements need to be client/project specific, team specific, problem specific

• there's a danger of getting tunnle vision, conentrating on the things measured to the expense of other important things

• only measure if there is some action that you could (and would) take as a result of the measurement.

Back to OtTwoThousandAndFourOutput.