Sprints

What is the challenge? Many teams have more than 1 person working on something. For example a couple of devs and a tester could be working on a complicated feature together. We currently can't do that. Additionally for performance reviews it's nic...

Ability to setup work schedules for Aha! Develop engineering teams. Similar to Capacity Planning Team Work schedules.

Need ability to track capacity (under / over allocations for time and pts) actuals for engineers, team, sprint, Releases, etc. This is based on the estimates for the requirement / feature within the sprint / release assigned to the engineer within...

Analytics and Reporting are part of Develop Advanced, and users in those accounts are able to save list reports. However, some teams use list reports as part of their backlog and sprint management process. They don't need sophisticated analytics, ...

Capacity for teams is currently available to set up at a daily, weekly, monthly and quarterly. It would be helpful for teams that are planning sprints, to be able to set a capacity for each item (Theme/epic/feature) per sprint. Once this is done, ...

What is the challenge? On some teams, only certain team members are allowed to start or close a sprint. Currently anyone with contributor access can open or close a sprint. What is the impact? Sprints are open or closed in error. Describe your ide...

I would like the ability to create, assign and manage sprints within a release, and link features to the sprint. Currently, I set sprints up as Phases within a release to do this. The issues with this workaround are: I cannot link a Phase from Aha...

RIght now the developers can add features to sprints without comsulting the product team or even managers. We would like to be able to lock a sprint.

Work moves in and out of my sprints day-by-day. I want a way to see only what's been added to the sprint so I can understand why they're not converging to their ideal state.

What is the challenge? If you have a record assigned to one sprint and it later gets pushed to a later sprint, the date range (when set to calculate from sprints) does not reflect the full time spent in multiple sprints What is the impact? ...