Items related to User Story Mapping
Agile user stories are deceptively simple things.
In agile software development approaches, they've become the most popular practice for describing software we'd like to build. The idea is simple: write on an index card or sticky note a single thing your software could do from the user’s perspective. Use this card, along with all the others you write, as "tokens for conversation" to work through all the details we'll need to understand to plan, construct and test software.
But, this is where things get complicated:
- What's the right way to phrase what’s written on a card? How much detail should I include?
- How "big" should a story be? A useful size from the user’s perspective, or small enough to easily code in a matter of days?
- To describe a typical piece of software it usually takes dozens, or even hundreds of these things. How do you make sense of a large backlog of user stories without losing the forest in the trees?
When this simple idea meets the harsh reality of a typical software project, it seems to fall apart. How could this possibly work? But, in practice it does--in some not-so-obvious ways.
In this short book those new to user stories will learn the basics of what a user story is and how to write and organize them effectively. You'll learn how to use stories to help with discovering what to build, plan valuable incremental product releases, and effectively manage software delivery. Those already working with user stories will learn approaches beyond the simple ideas they may have learned in a 2-day training class. Everyone will learn why the user story works so well for so many different uses and why this simple idea turns out to be one of the big innovations that’s emerged from agile thinking.
The book focuses on the emergent practice of story mapping as a way to help lots of small stories tell a bigger story that describes your software. Using a story map to help keep a cohesive big picture, you'll learn effective ways to leverage the map to discuss your ideas and plan your product’s delivery.
This short book demystifies user stories and explains how to pragmatically use them in your day-to-day agile practice.
"synopsis" may belong to another edition of this title.
About the Author:
Over his past two decades of experience, Jeff Patton has learned there’s no “one right way” to design and build software, but there’s lots of wrong ways.
Jeff makes use of over 15 years experience with a wide variety of products from on-line aircraft parts ordering to electronic medical records to help organizations improve the way they work. Where many development processes focus on delivery speed and efficiency, Jeff balances those concerns with the need for building products that deliver exceptional value and marketplace success.
Jeff has focused on Agile approaches since working on an early Extreme Programming team in 2000. In particular he specializes in integrating effective user experience design and product management practice with strong engineering practice. Jeff currently works as an independent consultant, agile process coach, product design process coach, and instructor. Current articles, essays, and presentations on variety of topics in Agile product development can be found at www.AgileProductDesign.com and in Alistair Cockburn’s Crystal Clear. Jeff is founder and list moderator of the agile-usability Yahoo discussion group, a columnist with StickyMinds.com and IEEE Software, a Certified Scrum Trainer, and winner of the Agile Alliance’s 2007 Gordon Pask Award for contributions to Agile Development.
"About this title" may belong to another edition of this title.
- PublisherO'Reilly Media
- Publication date2011
- ISBN 10 1449304559
- ISBN 13 9781449304553
- BindingPaperback
- Number of pages50
- Rating
(No Available Copies)
Search Books: Create a WantIf you know the book but cannot find it on AbeBooks, we can automatically search for it on your behalf as new inventory is added. If it is added to AbeBooks by one of our member booksellers, we will notify you!
Create a Want