Capacity planning

What is the challenge? The capacity report is great at showing your team's and/or user's capacity month by month, and highlighting any capacity conflicts. However, you sometimes want to view your capacity in different ways. For example the report ...

There is a current option on the Release Retrospective Report to view "Work completed (points)" which displays records associated with the release and totals with the "best estimate", using the initial estimate unless a detailed estimate is availa...

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.

I use named ranges for adding t-shirt size estimates to my epics. I want to roll these estimates up across epics to the associated initiative so I can easily understand the effort and costs of the full initiative. This roll-up works for other sce...

What is the challenge? Scenario: You have entered a detailed estimate and started logging work. You realize that there is a lot more work to do, so you update the remaining estimate to reflect the additional time required to complete it. Currently...

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

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

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

Currently, the capacity report only shows monthly capacity by team or individual, but that's about it. To keep capacity planning centralized in Aha and not require export of Epic data to do other aspects of planning, I'd like to see the following:...

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.