Story map

To create a story map

1. Identify user types and roles and their goals, needs, desires, gains, and pains
2. Solicit scenarios and stories—a day in the life of…
3. Distill story titles, validate with users and goals
4. Map out in story map

• Reemphasize the Business Vision and its expected outcome (from the PID?)
• Reiterate the Product Vision, Measurable Product Goals and output
  • Unique value of initiative
• Establish either (in the column headings of the story map):
  • a basic workflow or flow of activities
  • Epics
  • Key activities
  • major components
• Feature Thinning Guidlelines (Jeff Patton)
  • Make the top most row the first, smallest release.
  • Minimize a release so that to reap financial and risk reduction benefits earlier.
  • Top slice represents the minimal tasks needed to reach the Measurable Product Goals.
  • How can you split the stories into its smallest parts?
    • Can the features to support the task have
      • reduced safety?
      • reduced comfort?
      • reduced luxury?
      • options slated for a later release?
  • Which steps in the tasks are optional for now?

Sources

• product owner » Martien van Steenbergen's slide deck.
• Agile Product Design » Jeff Patton » The new user story backlog is a map.
• Agile Product Design » Jeff Patton » User Story Mapping » Quick Reference Guide.
• Winnipeg Agilist » Steve Rogalsky » How to create a User Story Map.
• InfoQ » Ben Linders » Product Backlogs with Process Maps or Story Maps.