Steve C's dashboard

"I think this split in usage is at the crux of why this question isn't easily resolvable."

Sure it is. Leave the current behavior in as the default and give me an "I know what I'm doing, make velocity X" override. Done. – Steve C, on January 23, 2010 00:35

Velocity is simply being asked to do too much, proof of which is the constant struggle people have matching their project reality up to it.

Is it an indication of business value completed? Why are developers determining business value? Is it supposed to be a prediction mechanism? If so, why can't I just nail velocity to some number if I've gone through a big chore+bug fixing phase - why must I live with the prediction part being broken when I'm absolutely certain that my team will be performing at a higher level?

Etc. I believe the answer is to open up tracker: make the types of stories user-configurable, make it so you can have multiple "velocity"-like measurements, again user configurable. This would lead to user experimentation and possibly innovation around agile planning. Wouldn't it be great if I could then share my tracker recipe on a forum like this and you could just plug it into your project?