Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Planned Velocity Calculation Question #26

Open
jonda03 opened this issue Oct 5, 2018 · 2 comments
Open

Planned Velocity Calculation Question #26

jonda03 opened this issue Oct 5, 2018 · 2 comments

Comments

@jonda03
Copy link

jonda03 commented Oct 5, 2018

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:

capture

But the APP shows very different Velocity numbers.:

capture

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 | [email protected]

@krmorse
Copy link
Contributor

krmorse commented Oct 9, 2018

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
Copy link
Author

jonda03 commented Oct 9, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants