[Agile Guide] – Story Mapping for Scrum

Problem:

  • You have a backlog full of stories.
  • You have a set of prioritized features that need to go out with your next release.
  • You are in need of a simple and quick way of viewing dependencies between stories and mapping features and tasks to their corresponding stories.

How can you easily connect the dots? With a story map.

Story maps are a great way to organize your backlog into a logical units for development. Karen Greaves has outlined a very simply way for you to build a story map and get back to workin’!

Her outline simplified:

What do story maps do?

  1. Group related stories together
  2. Break down stories from a user point of view
  3. Help stakeholders focus on priorities first
  4. Help set the goal for the release
  5. Help drive out requirements missed earlier in the planning phase

How do you do this?

  1. Chose user roles for the product
  2. Figure out what each user does within the product
  3. Map those user-roles to User Activity, User Task, and User Sub-Task (Color coordination helps here)
  4. Arrange activities in a swimlane to visualize workflow
  5. Meet with stakeholders and spot check the workflow
  6. On review, make changes
  7. Identify goals of the release with user-specific stories in mind

So bottom line? Story maps are great to elicit the core functionality of a product from a user-centric point of view. It gets the stakeholders to focus on what the customers or users must do in order for the product to be useful. All the other bells and whistles can come later.

Great stuff from Karen Greaves. Read more details below.

[VIA]

5 Responses to “[Agile Guide] – Story Mapping for Scrum”

  1. Pat
    December 29, 2010 at 9:46 am #

    Great article! How does one differentiate between a User Activity, User Task, and User Sub-Task?

Trackbacks/Pingbacks

  1. Tweets that mention Agile Guide] – Story Mapping for Scrum #agile #pmot -- Topsy.com - December 29, 2010

    [...] This post was mentioned on Twitter by Paul R. Williams. Paul R. Williams said: RT @agilescout: [Agile Guide] – Story Mapping for Scrum http://goo.gl/fb/fX9OH #agile #pmot [...]

  2. Tweets that mention [Agile Guide] – Story Mapping for Scrum | Agile Scout -- Topsy.com - December 30, 2010

    [...] This post was mentioned on Twitter by John Peltier. John Peltier said: Good ressource RT @agileEmissary Story Mapping for #Scrum – http://bit.ly/eGXO6m #agile [...]

  3. The Path to Product Success is Not a Straight Line | Agile Scout - August 17, 2011

    [...] and want to stick to it until the very end, even if that’s in the distant future. Why do so many stakeholders and project managers get so caught up in sticking to the original plan at the cost of change. [...]

Leave a Reply