user story mapping-hands-on // ux-day masterclass

USER STORY MAPPINGSTEPHANIE FÖHRENBACH - CHRISTIAN HELDSTAB – ZÜHLKE ENGINEERING AG

UX-DAY Mannheim 2016

User story mapping bridges the gap between two worlds

Stephanie Foehrenbach and Christian Heldstab, CHI 2016

WARM UP EXERCISE

Picture: Christian Heldstab User Story Mapping | Stephanie Föhrenbach, Christian Heldstab, Zühlke AG

Anatomy of a User Story Map• Backbone• Time• Activities• Tasks• Necessity/Priority• Walking Skeleton• MVP• Releases• User Groups

User Story Mapping | Stephanie Föhrenbach, Christian Heldstab, Zühlke AG

Picture: Christian Heldstab

THE BASICS


Picture: Christian Heldstab

User Story Mapping


Iterative and Incremental


Shared understanding

Taken from [RASMUSSEN] Stephanie Foehrenbach and Christian Heldstab, CHI 2016

A User Story Maparranges stories into an organized model.• Fosters a shared understanding

• Supports rich discussions

• Makes the workflow visible

• Shows relations between stories

• Helps to find gaps

• Provides context for prioritisation

• Plans releases in valuable slicesUser Story Mapping | Stephanie Föhrenbach, Christian Heldstab, Zühlke AG

EXERCISE: DOG DAY CARE


EXERCISE 1: CREATE MAP


PRIORITIZATION


”There’s always more to build than we have time or resources to build - always”.

Jeff Patton[PATTON] User Story Mapping | Stephanie Föhrenbach, Christian Heldstab, Zühlke AG

Minimize output to maximize outcome and impact

Adapted from [PATTON] User Story Mapping | Stephanie Föhrenbach, Christian Heldstab, Zühlke AG

Slice a release plan

Time

Prio

rity

First Release

Second ReleaseThird Release


The most basic functionality

Build the minimum necessary to use the feature in its most basic version. Build what you need to demonstrate it to stakeholder and user.

Most likely reaction of the user: “Hm, well at least it works…”

Add safety and variation

Add things that would make the feature safer to use. Add the ability to perform the user task in different ways. Support sub tasks that are optionally performed.

Most likely reaction of the user: “That’s now a job well executed, I can live with that…”

Add comfort and luxury

Add things that make the feature easier to use, faster to use, more desirable to use.

Most likely reaction of the user: “Wow cool, that’s really great and you thought about everything!”

Inspired by [MEZAROS], that describes four heuristics (storyotypes) which can be used to split stories. Stephanie Foehrenbach and Christian Heldstab, CHI 2016

Feature SplittingStart smallDon’t go for the fully blown functionality and user interface right at the beginning, but make sure it’s always useful and usable for the user.

Who needs to be involved in prioritization and slicing for

sure?

And why?User Story Mapping | Stephanie Föhrenbach, Christian Heldstab, Zühlke AG

Stephanie Foehrenbach and Christian Heldstab, CHI 2016User Story Mapping | Stephanie Föhrenbach, Christian Heldstab, Zühlke AG

EXERCISE 2: SLICE RELEASES


AND IN THE TRENCHES?


Story map and sprintsVisualise, refine and review.


Story maps are living documents

Adapt according to new learnings and UX insights


SFoehrenbach

DerDavoser


[COHN] Cohn, M. User Stories Applied. For Agile Software Development. Addison-Wesley. February 2009, Boston, MA, USA.

[MEZAROS] Meszaros, G. Using Storotypes to Split Bloated XP Stories. In Zannier, C, Erdogmus, H. and Lindstrom, L. (Eds.), Extreme Programming and Agile Methods – XP/Agile Universe 2004: 4th Conference on Extreme Programming and Agile Methods, Calgary, Canada, August 15-18, 2004. Proceedings (pp. 73-80). Springer Berlin Heidelberg. 2004.

[PATTON] Patton, J. User Story Mapping. Discover the whole story, build the right product. O Reilly Media. September 5, 2014, Sebastopol, CA, USA.

[RASMUSSEN] Rasmussen, J. The Agile Samurai. How Agile Masters Deliver Great Software. The Pragmatic Bookshelf. September 13, 2010, USA.

Stephanie Foehrenbach and Christian Heldstab, CHI 2016

user story mapping-hands-on // ux-day masterclass

Design