User Story Mapping with Easy Agile TeamRhythm

Purpose and objective of User Story Mapping

User story mapping is a visualisation and holistic understanding of the journey a customer takes with a product, from beginning to end. It includes all the tasks they’d typically complete as part of that journey. To expand on that, user story mapping takes all your user stories (across all your persona types) and assigns them to epics in the order that delivers the most value to the customer. From there, stories are prioritized and mapped to releases.

Key users (roles & responsibilities)

A team will collaboratively create a story map at the start of a project or product. It might be an entirely new product, or the product manager might want to pursue a new idea or feature as part of an existing product. Any team members responsible for the product experience should be involved.

• Product Owner: Plays a crucial role in user story mapping. They provide insights into the product vision, goals, and user needs.
• Development team: Actively participates in user story mapping, contributing technical expertise and providing input on feature feasibility and implementation.
• Scrum Master: Facilitates the user story mapping session
• Stakeholders: Business representatives, end users, and other relevant parties, may also be involved in user story mapping. Their perspectives and insights help shape the user journey and ensure that the product meets their needs and expectations.
• UX/UI Designers: Contribute their expertise in user experience and interface design. They help visualize the user journey, create user personas, and provide input on the design considerations for each user story.

User Story Mapping with Easy Agile TeamRhythm

User goal

So that I can commence work on a new feature, as a Product Manager, I want to be able to conduct a User Story Mapping exercise that maps the steps a user will take in my product when using this new feature.

Scenario

The addition of a new product feature has raised the need for a User Story Mapping ceremony to outline the steps that a user would take with the new feature.

Hierarchy planning

• Configure Hierarchy - set up the hierarchy so that it is able to be displayed on the TeamRhythm User Story Map

Epic level planning

• Use Quick Create to create new epics to group work

• Edit the details of an epic and save changes

• Set the rank/order of epics (drag and drop)

Issue level planning

• Use Quick Create to add a new issue

• Inline edit to change an issue summary

• Use drag and drop to change the position or order of issues

Issue details

• Configure issue card layout to display additional information on issue cards

Filters and Views

• Create a new filter using a component that is specific to the upcoming product increment & share the view with the team