Loading Profile...
Velocity overriding is not saving properly
When I adjust the velocity on my project, overriding it from the default to a number I enter myself, it all seems to save properly, and the iterations adjust accordingly, but then if I close the window and come back, it is reset to the default, my overriding is lost.
I'm in Safari 4 if that is related.
I'm in Safari 4 if that is related.
I’m fine, slightly annoyed
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
-
Inappropriate?Short answer is that the velocity override is not intended to persist.
From the FAQ entry http://getsatisfaction.com/pivotal/to...
You can play the "what if" game with other project velocities using the Override Velocity tool, but the changes are visible only to you and persist only until you revert them or close your browser. You cannot change the actual velocity, which Tracker calculates from previous iterations. Velocity is a reflection of how much your team can get done in a single iteration based on prior performance. Artificially inflating this number can lead to missed deadlines and stressed programmers. Your job is to estimate and prioritize your stories; let Tracker calculate what can be completed when based on impartial measurements of effort and time.
The company says
this solves the problem
-
Inappropriate?OK, that makes some sense, but here's the thing - the velocity it's calculating isn't really correct, it's 1, but that's because we had some cases left "in progress" for a few weeks when we didn't work on the project. Any suggestions?? -
Inappropriate?There is a notion of Team Strength built into Tracker.
http://getsatisfaction.com/pivotal/to...
Set your Team Strength to 0% for the last few weeks by clicking on the blue circular % symbol on the right edge of the iteration marker in the Done panel. Tracker will recalculate with the understanding that your lack of recent progress doesn't reflect a change in your velocity but a change in your team size.
I think that will accomplish what you want.
1 person says
this solves the problem
1 Comment Add a comment
This solves the problem
-
Awesome thanks!
EMPLOYEE
