RELATED IDEAS
Set capacity per team per release
Capacity for teams is currently available to set up at a 'global' level - number of hours per day per week.
It would be helpful for teams that are planning releases with multiple teams, to be able to set a capacity for each team per release.
Once this is done, comparisons for estimates at a feature level for each team can be made against the capacity for the specific release.
The capacity report would also be helpful to view per release, rather than per month in this case.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +10
8
MERGED
Capacity report: View capacity by release (rather than time)
To do proper sprint planning, I simply need to know what can be done in a sprint. The capacity report requires me to: (a) enter dates on all of my records, and then (b) add team estimates for all of my records before I can visualize capacity. It w...
0
Future consideration
+1 particularly on the capacity report per release (further benefit if it works on a roll-up release).
We love the Above the line/Below the line view of capacity for individuals but our manpowering planning fits into the Capacity for teams model. We would love to plan capacity by teams but view impacts per release.
Definitely a huge fan of this. Currently we're struggling to bring our wider organization of 160+ product managers on-board without this... We always seem to revert back to using a spreadsheet to determine capacities, which seriously detracts from the Aha value prop
Hope this gets implemented soon as will help significantly for us as we have a fixed schedule of releases advertised for the next year or so on an 8 week cycle and have the need to track different teams and the features they can do based on a percentage of a particular release capacity.