My ideas: Capacity planning

We'd like to estimate and plan releases based on velocity (rate of story point completion) rather than capacity (static value). This would enable more dynamic calculation of release capacity given a target release date and velocit(ies) over the d...

The Capacity report for teams provides the ability to see the available capacity per team per time period by hovering each cell/ It would be helpful to be able to include the available capacity per team in a list/pivot report. This would provide t...

In the same way that you are able to compute capacity estimates for teams on an initiative by features and master features, it would be helpful to compute from child initiatives. This would allow you to roll up team based forecasting up the hierar...

What is the challenge? Initial estimate for large capabilities (Epics) does not calculate based on estimates of child Features What is the impact? Confusion by engineering on the level of confidence expected for roadmap-level estimates Manually ad...

My agile development team uses story points for estimation. Once work is in progress, I want my developers to log work in time. This helps me understand where their time is going, and to inform future estimates for planning.

What is the challenge? I am trying to do capacity planning but there is no separation between Frond end and Back end start date (and it is affecting capacity planning) What is the impact? Describe your idea We plan our roadmap at the...

Today, if the detailed estimate is 0 then the Initial estimate is ignored in the best estimate calculation. I would expect us to ignore null/zero detailed estimate values if the initial estimate is >=1 when calculating the best estimate.

We would like to be able to view an individual's work schedule when reviewing capacity planning at an individual level. Capacity currently defaults to 8 hour day and workschedule is only supported at team level.

We have users stories mapped to requirements in Aha!. When viewing the capacity planning at a requirement level it uses the feature level start and end date, we want to see the start and end date of the requirement (Story). Also related to this in...

Currently, it's not possible to view the capacity report on the dashboard, only on presentations or a shared webpage. This is a major area of importance for us as we grow and update our procedures.