EU-MACS Coordinator: Prof. Adriaan Perrels,
parentPage= 783

The story mapping workshop should be lead by the Product Owner, or a User Researcher (as described above). It assists the Product Owner in collecting data that represents the needs of end-users and stakeholders. A user story workshop has the following phases:

  • Organization: Introduce the workshop’s structure
  • Introduction: The idea that underlies the system: what is the general objective that the
    system aims to reach?
  • User story generation: Each participant is asked to write down user stories on post-it
    notes. A user story has the following structure: “as a, I want to in
    order to ”. For example: As an, I want to be able to in order to.
  • User story presentation and grouping: Each workshop participant presents the user
    stories that she came up with and posts them on a wall. User stories that in some way
    belong together are clustered on the wall and are given a group name. These group
    names are referred to as “epics” in Scrum.
  • Assigning value: When all post-its have been posted, the person who leads the
    workshop goes over each of the user stories with the other participants and writes one
    of the following categories on it: must have, should have, could have and won’t have.
    This is a very important part of the workshop, as feature creep almost always occurs.
    Feature creep refers to the fact that people have the tendency to assign functionality to
    a system that does not provide much value. It is therefore essential for the project to
    focus first on the user stories that deliver the most value.
  • Prioritization and strategic release of user stories: Through the prioritization of the user stories, different releases can be planned of the system, focusing first on the high-
    impact user stories.