RELATED IDEAS
Merged idea
This idea has been merged into another idea.
To comment or vote on this idea, please visit APP-I-594 Detailed Capacity Planning.
Add Capacity Planning to Roll-up Release
Merged
Ability to define capacity at a roll-up release level to allow capacity planning for teams working across products within a release cycle.
-
ADMIN RESPONSESep 26, 2024
Thank you for the idea. The vote count for this idea is inaccurate because it was originally merged into a broader idea related to capacity planning. Since this idea was submitted, we have greatly improved our capacity planning features. More details on what is possible can be found here.
We want to learn how important capacity planning for roll-up releases is among customers. So we have created a new idea to track this specifically. If this is important to you, please go and vote on this new idea and let us know how it would help your team.
We are going to merge this idea back into the broader capacity planning idea now, which will update the status to shipped. Thank you!
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +322
166
MERGED
Allow capacity planning by product line
We share development resources across several products, and capacity planning by product is of limited value. Enabling an option to set and track of capacity at the master release level would be very helpful. Ideally, capacity within subreleases w...
7
Shipped
© 2024 Aha! Labs Inc.•All rights reserved
+1 PLEASE
I second that, see my remark on "detailed capacity planning", for the same reason.
However: capacity should also be regarded independent of any release - as this is reality -. You may have resources working on parallel releases. What you really need is to see when an allocation (feature/reqs) done from within whatever release overloads a resource - regardless the release.
All releases that have features outstanding at the moment the resource is overloaded should be marked for review. (So Axosoft's Release Planner, or Microsoft Project's Team Planner)
Definitely got my vote. Though I would define it more generically: add capacity planning on any release level.
Booyah!
I hit this hurdle recently too.
I have a relatively smallish cross functional team that works across several related, but independent, products within a portfolio. Currently i have to track capacity for each product/version in Excel to ensure i don't oversubscribe the team for a sprint.
It would be good if Master Releases could represent sprints, and the estimates for each product/version contained in the Master Release was rolled up into the Capacity for that Master Release.
That way, at the Master Release level, for example, i could see that i had used up 100 out of 150 hours, across 5 projects, so still had spare capacity.