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...
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...
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 sprin...
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...
This idea is to update capacity for teams to support the ability to estimate in story points. You are currently only able to estimate in hours, people, or cost.
Estimations is an important factor in our prioritization and decision process and a weak point right now in Aha! Right now Aha! surprisingly does not allow to build a simple list report that could show all initiatives/epics/features with no estima...
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.
Please add an additional unit of "T Shirt Size" to support capacity planning. When planning for a longer time horizon (e.g. annual planning), using story points, people or hours is not sufficient. We estimate initiatives & epics using T Shirt ...
Display the capacity bar on features board > epics tab
These capacity bars disappear when you swap to the "Epics" tab of the features board. Now that we can configure releases to use the epic's estimates, we want to display this bar on the board.