Capacity planning

Our engineers do their dev work at the Requirement level in Aha!. Capacity Reporting would only benefit us if we could track time/points associated with Requirements (not Features) to accurately do resource planning of our engineers.

We are a mature Agile team that uses story points exclusively to estimate the work done in each sprint. The new capacity report feature rollout is excellent, but it does not allow for story points to be used as the method of estimation for a sprin...

Currently it's possible to drag "estimate" over to the feature cards (in Features->Workflow). Our company doesn't use estimates heavily, but we do log rough time taken on a task. This would allow myself (as a developer) a quick glance to see wh...

We're using Aha with Azure DevOps integration. We’ve mapped the Estimate field in Aha with an estimate field in Azure DevOps. Our estimation process is basically as follows: * Product Manager creates Feature in Aha * Product Manager send RFC...

At Intuit, we are looking at two different effort values - estimated points at solution completion, and actual points based on development team's user stories during implementation. To be clear, we look at feature allocation with estimates based o...

Hello, in my company we have several development teams working on the same product. Therefore we create a custom scorecard to be able to have an estimate for each team involved in each feature. We also have a custom field with the teams involved i...

Often when new Feature requests come in they are at, what we consider to be the Master Feature level...basically an Epic. For future releases, we hold a Release Planning session where our engineers apply high level estimates to Master Feature that...

At the moment it is very easy to over- or under- plan high level capacity by having releases overlap, or by having big gaps amongst releases. This is very dangerous, and either results in unrealistic expectations being set to stakeholders and/or c...

The "Release Capacity" dialog allows users to enter in a capacity amount. however, the dialog doesn't much help in figuring the hours, days nor weeks. For example, I needed to manually calculate that there are 22 working days in July 2016 by count...

It would be nice if I could customize what a day means in actual hours so that when our work integrates with JIRA it doesn't blow up the hours the wrong way. For example - a day for us means 10 hours of work. However, I can't customize that so whe...