I found out that in order to assign a user from Aha to Trello you can use Tags to let Trello users know that a card is assigned to someone. However it is not really assigned to someone, it is just a tag( Capture5.png #2). Once in trello you have t...

What is the challenge? having to use the whteboard to create from scratch a template for a product biref What is the impact? a roduct person in a mangerial prositions produces a lot of prodct artifacts per month, including Product Briefs andPRDs D...

Sometimes I underestimate my To-dos and would like to convert them into features associated to a release.

What is the challenge? Aha! defines the fundamental unit of work as a Feature. From a Product Management point of view, it is a fundamental unit of functionality (not work). For development, the fundamental unit of work is a Story in SAFe. Becau...

What is the challenge? When dates (ex: Release dates) change, it has a cascading impact to other functions. Allowing automation to update custom fields would help manage the impact. What is the impact? Without the automation, users are ask...

What is the challenge? We often have the use case where we need to connect an Aha! epic to an existing Jira record, and that Jira record will also likely have child tasks/stories. The existing connection logic will only sync with the epic record, ...

Who would benefit? Any client, but especially those practicing SAFe What impact would it make? Make it very clear which features can be pulled into a PI and which won't, based on capacity, so negotiations can commence! How should it work? On the C...

We use the initial estimate field for early product planning. While the "No detailed estimate" field helps for our detailed planning stage, we want similar functionality that checks for missing initial estimates to support our earlier planning.

It is great that I can copy the URL of an existing record to create an object on a whiteboard (along with an attachment link). However, I'm not able to edit the text or change the font size, which is something I'd want to do. As whiteboards use th...

The release retro report currently uses only a single (pseudo) milestone: when development started. Some teams want to measure changes in the release relative to several milestones within a release, such as a beta launch, or code freeze.