Capacity planning

What is the challenge? The way that capacity planning currently works is that you create a schedule with a static number that you label velocity, but isn't actually velocity. Each team's velocity is different and applying a blanket "each person ...

Who would benefit? Teams using capacity planning for teams, planning with named ranges (e.g. t-shirt sizes) What impact would it make? Today, I am only able to report on the specific estimate associated with a record, not the named range value tha...

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.

The improvements to capacity planning are making it much easier to do team and individual capacity planning. I would love to see an end state where I can provide a set of information on a record and have Aha! calculate the optimal plan for me. The...

It would be valuable to configure the capacity planning view so that work items that are blocking another one are allocated first on the timeline for a team or team member.

Our company needs the ability to track CapEx hours as well as utilize the story points on the features. It would be nice to have a way to track CapEx hours at the requirements level.

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...

We do all of our assigning in Jira, and in fact only sync epics between Aha and Jira, so adding an assignee in Aha doesn't make sense for us as you don't assign a dev to an epic, even in Jira. We assign to the task/sub-task. Having to add an assig...

What is the challenge? Non-working days are defined within a work-schedule. To spot a non-working day on the capacity report you need to look at a team or individual who has an estimate entered over that non-working day. This looks the same as a w...

We're adopting a more flexible release strategy that is feature/initiative driven, not time boxed. It would be great to be able to generate a burndown chart for an initiative (even better: overlay several initiatives) so we can project/monitor our...