Loading Profile...
Override velocity after restarting stalled project
After development was stalled on my project, the Velocity goes to 1. Now we are starting again, it's putting one task for each 5 or 6 iterations, and the iterations default to closed. It's very confusing and not very helpful. How can I override that for all users?
I’m happy
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?I agree. This goes for coming out of weeks with a bunch of bug-fixing. We know for a fact that we can execute at "normal" velocity, so we have to cook the books with Team Strength to make Tracker a reliable planning tool once again.
-
Inappropriate?Unfortunately it's not possible to override velocity for others, but you can use a combination of iteration length override and team strength. Take the iteration where that "stall" began, change it's length to however many weeks to stall continued for, and them change the team strength for that iteration to something that reflects the relative amount of energy that was being devoted to the project. You can make it 0, if no work went on at all.
This should align Tracker's view of the project with reality. -
Inappropriate?Could we maybe just have a way to enter in a velocity number and have velocity be that? i.e., "set velocity to X" and you enter the number in the box. In fact you could just add another button to velocity override to "make the override permanent" - that would be a fairly elegant way to accomplish it.
EMPLOYEE
