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 does not aggregate from child projects #21

Open
jcwaco opened this issue May 13, 2018 · 1 comment
Open

Planned Velocity does not aggregate from child projects #21

jcwaco opened this issue May 13, 2018 · 1 comment

Comments

@jcwaco
Copy link

jcwaco commented May 13, 2018

Hello Kyle,

I love the updates to this App!

However, the Planned Velocity (shown in units of Feature Points) does not aggregate as you select higher level 'Projects' in your hierarchy. It appears to take whatever Planned Velocity is on the currently selected 'Project' for the right (YY) side of "XX of YY Feature Points". At higher levels in your project hierarchy this is often 0 as you are relying on the aggregation of the Release velocities of the Teams in leaf level projects to aggregate up.

See the Release Planning page or App to see how it does this aggregation.

screen shot 2018-05-13 at 1 55 40 pm

@krmorse
Copy link
Contributor

krmorse commented May 14, 2018

hmm, yep that does seem wrong. i'll look into it...

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