My ideas: Delivery

Overview Teams using Aha! Roadmaps + Develop find that people get confused by the two different status fields: Workspace status Team status We should improve the UX to better represent that the team status is (typically) a more granular breakout o...

What is the challenge? There currently is no way to calculate SLEs inside of Aha!. What is the impact? I have to export the data to a spreadsheet and then calculate it myself. Describe your idea Add a report that looks at team performance and calc...

What is the challenge? The current order is what you did and what you planned. What is the impact? It's harder to read this way and you have to check yourself each time to remember the order. Describe your idea Showing planned then actual is a muc...

What is the challenge? While that report has value, many people find it hard to read. There is information that we could show on that board that would allow people to make better decisions. What is the impact? Most people ignore this board, missin...

Improve the way the velocity report within Develop handles records that are re-estimated, added or removed during an active sprint. Specifically would like to see: - Ability to re-estimate a record after the sprint has started without any adverse ...

On Aha Develop I'd like to send an entire engineering backlog (/parking lot) to a sprint. Alternatively, sending the top X items (by number or effort estimation). This will allow us to easily add a prioritized backlog to a sprint

Aha! Develop provides support for sprints. I'd like to see a burndown chart for those sprints so I can ensure my team is on-track.

Who would benefit? Senior Leadership What impact would it make? I can't easily share this info outside of the AHA Use Community without cutting and pasting using a snipping tool and its not efficient How should it work? This info needs to be share...

We've been using the default sprint description template to track our retrospectives. It would be great to create retro to-dos on the sprint record to capture and track clear next steps.

Seems to be a bug where the number on the column, which used to indicate the count, is not accurate: