Story Mapping is a better way to work with Agile User Stories
User Story Mapping is a dead simple idea. Talk about user’s journey through your product building a simple model that tells your user’s story as you do. But it turns out this simple idea makes working with user stories in agile development a lot easier.
More importantly it’ll keep your users and what they’re doing with your product front and center in your products. That’s better than getting lost in feature arguments like what normally happens in software development. I’m not making any promises here, but if you use Story Mapping, I believe your products will ultimately be better.
From this page you can get to a number of resources on and off this site that’ll help you with story mapping.
|Read This Book: In it, you’ll learn about the practice of story mapping and how user stories are really supposed to work in Agile Development. Read my blog post about the book or just go Buy My Book (Yes, I wrote it).|
|Read This Blog Post: I wrote this post before I wrote a book about mapping. This post describes Story Mapping and has been widely used and referenced. The New Backlog|
|Read This Article: This old article, How You Slice it, was my very first article on the idea – even before it was called Story Mapping.|
|Download Some Quick Reference Guides: I’ve built some simple quick references I use in classes and workshops. Take a look at the Story Mapping Quick Reference, and at the User Story Quick Reference.|
|Check Out Story Mapping Slide Presentations: An archive of new and old. View slides.|
|Take a Look at this Presentation from FlowCon 2014: Why Documents Fail; What You Can Do About It FlowCon Now|