User Story Mapping for Features/Requirements

Admins should have the ability to chose which records are in the User Story Mapping. We structure Aha! so that User Stories are at the Requirement Level so it makes sense for us to view as Features/Requirements

 

We don't use Master Features & don't want Aha! forcing the record type simply because you are leveraging the tool as this will cause user confusion.

  • Robyn Diamond
  • Jul 11 2019
  • Future consideration
Release time frame
  • Attach files
  • Rich Cernech commented
    19 Aug 15:10

    Deriving from this article https://support.aha.io/hc/en-us/articles/202001137-Aha-initiative-feature-and-requirement-mapping-for-Jira-Greenhopper-, we are capturing Features as Epics and Requirements as User Stories. This has worked well until we are now trying to leverage your User Story Mapping tool. I believe the 'Steps' in the tool are Features in our world and the Feature details are Requirements to us. Especially as we have integrated to Jira with Feature -> Epic and Requirement -> User Story.  We feel we need the ability to story map with requirements so that they can seamlessly flow to Jira as User Stories when dev work is ready to commence.  Thanks!

  • Guest commented
    28 Aug 12:01

    I couldn't agree more!

    User story mapping, should map user stories, and not EPICS.   If you could achieve this flexibility, then I'm sure more Aha users would be able to benefit.

  • Charlene Brennan commented
    29 Aug 12:08

    We use requirements in the same manner as Rich.  We support this change.

  • Iqbal Mohammed commented
    29 Aug 14:49

    I cannot agree more. It is very obvious that user story mapping should allow user stories (requirements) to be added.

  • Doug Brunner commented
    06 Sep 21:02

    100% agree. We currently have a hierarchy in DevOps of Epic (Master Feature) >> Feature (Feature) >> UserStory (Requirement). In order to adopt Aha! Story Maps we will need to move our 'story' description into the Feature and create more Features to make sorting meaningful. Also, Aha! currently restricts a one-to-one relationship between a Master Feature and a Step which is limiting as it is common for many Features under the same Master Feature to span multiple Steps in the same Story Map.

  • Guest commented
    15 Oct 19:50

    Agreed... we want to document the larger customer user map story for an EPIC at feature level and then do another level of that user story map at the requirements/story level... having both abilities will be highly benefits in creating strong product narratives for all team to engage with.