Capacity planning

We would like the ability to book soft allocations - team member or unnamed resource has been attached and is tentatively penciled in to work on the project. When there is less certainty about who/time that will be involved in the project it nice ...

Development is largely a shared resource and it is very common for development teams to be re-balanced at the end of each program increment (PI). Specifically, developers will often be re-assigned from their current team over to a new team for the...

What is the challenge? If default teams are selected for a standard team scenario, records will show for a team in the capacity planning report, even if that team doesn't have an advanced estimate for that record What is the impact? Capacity plann...

Who would benefit? Customers using capacity planning for teams whose fiscal year does not align to the calendar year What impact would it make? Today, the capacity report does not properly attribute quarterly estimates when the team's fiscal year ...

The built-in Estimate field on the Feature card shows no hint on how to enter data. New users are left to guess what to enter. Interestingly, the "Log Time" modal has this hint (see att). Request is to add hint-text to the "Estimate" field on the ...

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

Who would benefit? Anyone using an integration with time based settings What impact would it make? Showing accurate estimates in Aha that match Azure Dev Ops How should it work? The estimate and effort fields in ADO are numeric. Our teams are esti...

Why: This would allow variable team capacity per month/week etc. With current state of capacity setting, teams cannot account for changes in resources for partial project spans, member additions, losses, changes etc. This makes this feature less v...

We use custom fields to capture KPIs and other key strategic data when creating and maintaining capacity forecasts. There are no facilities - CSV or API - to import these data points which is causing significant work for our product teams. This is...

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