- 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?
- Group related stories together
- Break down stories from a user point of view
- Help stakeholders focus on priorities first
- Help set the goal for the release
- Help drive out requirements missed earlier in the planning phase
How do you do this?
- Chose user roles for the product
- Figure out what each user does within the product
- Map those user-roles to User Activity, User Task, and User Sub-Task (Color coordination helps here)
- Arrange activities in a swimlane to visualize workflow
- Meet with stakeholders and spot check the workflow
- On review, make changes
- 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.