Paperback, 322 pages
English language
Published Nov. 21, 2014 by O'Reilly and Associates.
User story mapping is a valuable tool for software development, once you understand why and how to use it. This insightful book examines how this often misunderstood technique can help your team stay focused on users and their needs without getting lost in the enthusiasm for individual product features.
Author Jeff Patton shows you how changeable story maps enable your team to hold better conversations about the project throughout the development process. Your team will learn to come away with a shared understanding of what you’re attempting to build and why.
• Get a high-level view of story mapping, with an exercise to learn key concepts quickly • Understand how stories really work, and how they come to life in Agile and Lean projects • Dive into a story’s lifecycle, starting with opportunities and moving deeper into discovery • Prepare your stories, pay attention while they’re built, and learn from …
User story mapping is a valuable tool for software development, once you understand why and how to use it. This insightful book examines how this often misunderstood technique can help your team stay focused on users and their needs without getting lost in the enthusiasm for individual product features.
Author Jeff Patton shows you how changeable story maps enable your team to hold better conversations about the project throughout the development process. Your team will learn to come away with a shared understanding of what you’re attempting to build and why.
• Get a high-level view of story mapping, with an exercise to learn key concepts quickly • Understand how stories really work, and how they come to life in Agile and Lean projects • Dive into a story’s lifecycle, starting with opportunities and moving deeper into discovery • Prepare your stories, pay attention while they’re built, and learn from those you convert to working software
I love story mapping as a technique, and this book is a great introduction to the hows and whys. But it's probably about twice as long as it needs to be. I recommend you read it all, but skim the second half quickly.
