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.
Allow capacity report to be configured using story points
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 spri...
Ability to add "Logged Time" to feature cards, in the same way "Estimate" can be shown.
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 w...
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 ...
Need to track estimates and actual story points separately, and display on Feature board
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 ...
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...
Add the concept of "planning increments" to help manage capacity more realistically
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...