 | this work is in progress and as 0.8b3 XPlanner calculated velocity is incorrect |
As part of release planning, we are trying to build velocity calculation support at both iteration and release level. The calculation follows yesterday's weather.
As we see it there are 2 ways to calculate velocity using yesterday's weather, a simple and more elaborate way:
- Constant effort: in that mode you will not explicitly manage the time spent while been in vacation, sick, other projects... i.e. any full time activity not contributing to the project, as part of velocity calculation
- Variable effort: in that mode you try to take these activities into account
Velocity calculation
Variable effort
In the following table, "days" corresponds to a full "work day" of one team member.
| Days worked | Actual number of days worked by all team members in one iteration. |
| Days available | Estimated numbers of days of all team members available to work on the project in that iteration. Follow the same calculation as Days worked |
| Estimated daily velocity | Number of units (story units or task hours) a team member complete in one work day |
| Team velocity | Number of units the entire team can complete in one iteration |
Example:
- 1 week long iteration of 3 full time people: days worked/available = 15 days.
- 1 week long iteration of 3 full time people with one of them taking 3 days of vacation: days worked/available = 12 days
Note: days worked and days available may be different due to unplanned circumstances.
XPlanner velocity calculation
Team velocity iteration n = Completed units iteration n-1 X Days available iteration n / Days worked iteration n-1
