Loading Profile...
Team strength and velocity calculation
I set my team strength to 300% for an iteration and got about 3x my normal amount of work done during that week. For calculating future velocity, though, Tracker took ALL the points I did during that iteration into consideration instead of 1/3 of them. Shouldn't it take my abnormal team strength during that iteration into account when calculating my average velocity?
I’m silly
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?Joey, I was able to find a project via your unique last name, and I do see a recent iteration with a 300% Team Strength, so I think it's the right one. The velocity is the running average of four iterations and is currently 11.
The three iterations that have passed so far have velocities of 17, 10, and 30, with the 30 point iteration being at 300% Team Strength, and thus really a 10 point iteration. That should mean a velocity of 12 [(17+10+10) / 3 = 12.3]. If Team Strength were being ignored, it would mean a velocity of 19 [(17+10+30) / 3 = 19]. So your velocity of 11 is closer to the one that correctly uses Team Strength, but it still isn't correct.
I'll file a bug with the team, but I'm guessing that once your fourth iteration is complete next week the velocity calculation will be correct.
I’m hopeful the bug will be easy to fix
-
Inappropriate?Hey Sean,
Thanks for the great response!
You're right, once I get into the project view my velocity shows up as 11, and it does seem to be using that number based on the amount of work that it put into my current iteration.
When I look at my project in the dashboard, however, it shows the number in the top left corner of the project button as '19'. This is supposed to be my velocity, right? This was the number I was looking at originally that had me confused.
Thanks again for the reply. I'm new to this whole philosophy of project management, so I thought it might be feature and not a bug and I just didn't understand how it was supposed to work. I really appreciate you taking the time to explain it for me.
Joey
I’m thankful
-
Inappropriate?The dashboard is clearly taking the wrong number, without Team Strength. I'll file a new bug with the team about that issue.
Please do follow up here with your velocity after iteration 4 ends. I'm curious to see if at least the velocity in the project settles down.
-
Inappropriate?Hey again,
I did 13 points last iteration, so my velocity should be 12.5 now, since I'm taking the average of the previous four iterations (17+10+10+13) / 4 = 12.5). However, in the project view it shows my velocity as 11 and in the dashboard it now shows it as 17.
Not a big deal, just wanted to follow up :) -
Inappropriate?Thanks Sean and Joey
I think that the Average is wrong because it does not count the strength in iterations.
Let me show you an example, Supose a full week of holidays(0% strength that week). Supose a velocity of 9 during the las iterations:
I think that the average now is: (10+10+10*0) / 3 = 6.7
But the average should be pounded also with the strength: (10+10+10*0) / (1+1+1*0) = 10
In case of two weeks of holidays it will be (10+10*0+10*0) / (1+1*0+1*0) = 10
Supose that the strength for a week is 50% due to holidays or other project affairs, the average should be (10*10*10*0.5) / (1+1+1*0.5) = 10
In Sean's example average should be: (17+10+10*3) / (1+1+1*3) = 11.4
So the average should be calculated using the real dedication.
Jorge
I’m happy
EMPLOYEE
