More flexibile hierarchy with story mapping

Who would benefit?

All user

What impact would it make?

For Aha:

Increase value proposition for Aha relative to other tools like whiteboarding tools and Atlassian Confluence

For Aha customers:

• Better alignment with customers unique requirement models and practices

• Tool consolidation

• More efficient translation between a concept/vision and functional requirements

• More efficient transition between product management and engineering

How should it work?

1. User can add an additional hierarchy tier to the story map

2. All 4 tiers of Aha's requirement model are supported (initiative, epic, feature story)

We often use story mapping as a way to breakdown epics into logical, incremental features and identify initial stories.

However, the current tool is limited because we are not able to go down to the story level. We also typically don't need to user the step capability.

To overcome this limitation, we use whiteboarding tools for our story mapping.