Mastering the Requirements Process, 4th Edition
by James Robertson, Suzanne Robertson, Adrian Reed
35
Story Map
The story map is a better way of organizing your backlog of stories. It provides a structure that is an understandable overview of the solution to be implemented—understandable to the business stakeholders as well as the development team. The stories for the map are those that we described in Chapter 28, Writing Good Stories. You would have written these as you went about your requirements discovery. A backlog, more correctly a product backlog, is a collection of stories awaiting development. Here we are discussing how your requirements repository could be a story map, and how that can be an effective way of collecting and communicating your stories.
We attribute the story map to Jeff Patton; he introduced them in his book User ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access