Planned Velocity Calculation Question

[jonda03]

Hi Kyle,

We just started using this APP and love it for the most part.

One question that came up is about how the Planned Velocity numbers are calculated.

The Release Metric report in AC shows these Velocity numbers for the Corvus team:

But the APP shows very different Velocity numbers.:

Why the difference in Velocity numbers? We're wondering what metrics the APP uses to calculate the numbers for its Planned Velocity dashboard.

Appreciate any insights you can provide.

Thanks,
Dave...

David R. Jones
Sr Principal Product Owner
IT Operations and Automation
Pittsburgh Mainframe Center of Excellence

CA Technologies | 750 Holiday Drive, 3rd Floor | Pittsburgh, PA 15220
Office: 412-494-1332 | David.Jones@ca.com

[krmorse]

I just looked through the code, and it's calculating that as the sum of all the PreliminaryEstimates of the features in the release divided by the PlannedVelocity of the Release. That's why it doesn't match what you're seeing. Seems like we could probably make it smarter. Either sum up all the story estimates, or use refinedestimate, or something like that, using PreliminaryEstimate as the fallback. What would you suggest?

[jonda03]

Thanks for checking into this! I would suggest using the same metrics that are used on the Release Metrics App, that way, they'd be in sync. Thinking would be something like Planned Velocity Points verses Accepted User Story Velocity Points.