User Stories Applied: For Agile Software Development (Addison-Wesley Signature Series) (Paperback)

by Mike Cohn (Author)

Editorial Reviews

Product Description
The concept of user stories has its roots as one of the main tenets of Extreme Programming. In simple terms, user stories represent an effective means of gathering requirements from the customer (roughly akin to use cases). This book describes user stories and demonstrates how they can be used to properly plan, manage, and test software development projects. The book highlights both successful and unsuccessful implementations of the concept, and provides sets of questions and exercises that drive home its main points. After absorbing the lessons in this book, readers will be able to introduce user stories in their organizations as an effective means of determining precisely what is required of a software application.

From the Back Cover

Agile requirements: discovering what your users really want. With this book, you will learn to:

• Flexible, quick and practical requirements that work

• Save time and develop better software that meets users' needs

• Gathering user stories -- even when you can't talk to users

• How user stories work, and how they differ from use cases, scenarios, and traditional requirements

• Leveraging user stories as part of planning, scheduling, estimating, and testing

• Ideal for Extreme Programming, Scrum, or any other agile methodology

----------------------------------------------------------------------------------------------------------

Thoroughly reviewed and eagerly anticipated by the agile community, User Stories Applied offers a requirements process that saves time, eliminates rework, and leads directly to better software.

The best way to build software that meets users' needs is to begin with "user stories": simple, clear, brief descriptions of functionality that will be valuable to real users. In User Stories Applied, Mike Cohn provides you with a front-to-back blueprint for writing these user stories and weaving them into your development lifecycle.

You'll learn what makes a great user story, and what makes a bad one. You'll discover practical ways to gather user stories, even when you can't speak with your users. Then, once you've compiled your user stories, Cohn shows how to organize them, prioritize them, and use them for planning, management, and testing.

• User role modeling: understanding what users have in common, and where they differ

• Gathering stories: user interviewing, questionnaires, observation, and workshops

• Working with managers, trainers, salespeople and other "proxies"

• Writing user stories for acceptance testing

• Using stories to prioritize, set schedules, and estimate release costs

• Includes end-of-chapter practice questions and exercises

User Stories Applied will be invaluable to every software developer, tester, analyst, and manager working with any agile method: XP, Scrum... or even your own home-grown approach.

See all Editorial Reviews

Product Details

• Paperback: 304 pages
• Publisher: Addison-Wesley Professional (March 11, 2004)
• Language: English
• ISBN-10: 0321205685
• ISBN-13: 978-0321205681
• Product Dimensions: 9.1 x 6.9 x 0.7 inches
• Shipping Weight: 15.2 ounces (View shipping rates and policies)
• Average Customer Review: 4.8 out of 5 stars See all reviews (44 customer reviews)
• Amazon.com Sales Rank: #9,963 in Books (See Bestsellers in Books)

  Popular in these categories: (What's this?)

  #69 in	Books > Computers & Internet > Computer Science > Software Engineering
  #89 in	Books > Computers & Internet > Web Development > Programming
  #98 in	Books > Computers & Internet > Programming > Software Design, Testing & Engineering > Software Development

• This item is part of The Signature Series.

Customer Reviews

Most Helpful Customer Reviews

29 of 30 people found the following review helpful:

5.0 out of 5 stars The user story bible, July 25, 2004

By	Lasse Koskela (Helsinki, Finland) - See all my reviews (REAL NAME)

'User Stories Applied' was a book that long stood on my Amazon wish list with a 'must have' rating. I'm not disappointed. I loved the book. Now let me explain why.

First of all, running the planning aspect of an XP project, for example, well is essential for reaping the benefits of agile software development. Yet, relatively little has been written to guide practitioners in doing that. I, for example, have made all the mistakes Cohn enumerates in the chapters for guiding the user towards writing *good* user stories (usually more than once). These sorts of things make you realize you shouldn't put the book on the shelf to gather dust! The author doesn't cover just writing good user stories, but the whole spectrum from putting together the customer team to estimating stories to discussing the stories to writing acceptance tests for the stories.

Second, it's a pleasure to read. The structure makes sense, each chapter is followed by a useful summary, and there's a set of questions -- along with answers -- to make sure you understood what the chapter talked about. Usually these kinds of Q&A sections simply force me to skip them over. The questions in this book did not. I read each and every one of them and I think there was only one set of questions that I did 'pass' with the first try, usually having forgotten some rather important aspects to consider (concrete evidence of their usefulness to me). To finish, the last part of the book, an example project, nicely ties together all the threads.

As usual, there were some things I experienced not so well. I believe the chapter on applying user stories with Scrum could've been left out without breaking the plot. Also, I think a typical user wouldn't have been bothered about dropping the appendix introducing Extreme Programming.

In summary, this is the book to get if you're involved with user stories. I had to pause reading every few pages to scribble down some specific tips. I'm confident that you will too.

14 of 16 people found the following review helpful:

5.0 out of 5 stars Finally! Practical advice on writing user stories, and more, March 14, 2004

By	Lisa Crispin (Denver, CO United States) - See all my reviews

This excellent book is a must-have for anyone on an agile team - developers, testers, business experts, analysts - and for anyone who struggles with requirements, planning, or estimating on any software project.

User Stories Applied is easy to read and digest. As the title suggests, its techniques are easy to apply and deliver huge value. Each chapter summarizes developer and customer responsibilities, and has questions whose answers are provided in an appendix. The book is full of real-life, concrete examples, allowing you to learn from the successes and failures of others.

This book will give you many tools to help your projects succeed. Just a few of the most valuable topics:
When are user stories too big, too small, too detailed, too general, too open ended, when are they not user stories, and how to correct all these.
Why use user stories.
How to handle requirements for infrastructure, performance, qualitative aspects, UI.
How to ask questions to elicit requirements.
How to cope when you don't have `on-site customers'.
Practical ways to estimate stories.
Monitoring velocity and progress.
When to keep and when to discard artifacts.

Mike explores the differences between stories and other techniques for delivering requirements: IEEE 380, use cases, scenarios. He points out many positive side effects of user stories, such as encouraging participatory design and tacit knowledge accumulation.

I particularly like that the book emphasizes the team's responsibility to successfully complete each iteration. I enjoy Mike's illuminating bits of wisdom, such as the "everything takes 4 hours" example. I love the comprehensive example in Part IV. No matter what your level of experience, you'll put the ideas in this book to immediate and productive use.

7 of 7 people found the following review helpful:

4.0 out of 5 stars For XP enthusiasts, November 4, 2005

By	Ugo Cei (Pavia, PV Italy) - See all my reviews (REAL NAME)

Writing user stories is one of the twelve practices of the XP software development methodology. User stories summarily describe features of the software that must be developed, from the point of view of the user. This means that no implementation detail is present on stories.

As with all the XP practices, the emphasis is on traveling light, producing only those artifacts that are absolutely necessary. Thus, user stories contain a brief description of the feature as a reminder, to the developers and to the customer, that sometime in the future they will need to meet and flesh out the details. This is in contrast to techniques like use cases, which might seem similar but are much more formal and rich.

User stories also play a fundamental role in the planning game, one of the other XP practices. During the planning game, the development team and the customer together discuss the stories, the developers estimate the time necessary to implement each story, in terms of story points and the customer prioritizes them. During the next iteration, developers will implement those stories that the customer deemed more urgent, up to a number whose total sum of points does not exceed the estimated team velocity.

All of this is explained in a couple of the XP series books, namely Extreme Programming Explained: Embrace Change and Planning Extreme Programming You'd better have already read at least the former of those before picking up Mike Cohn's book.

User Stories Applied does a good job explaining in detail what user stories are, what goes into them -and what doesn't -, how they should be estimated and what to do with them after the stories have been implemented.

There's a lot of good sense advice in this book, which might induce someone to think that user stories and all other XP practices are just a bunch of generic suggestions that you might apply or not, as you wish. That's certainly not true, as XP is a methodology whose effectiveness lies in the combined action of all the practices when they are taken to the limit. This takes determination and discipline and, in my experience, it's just too easy to fall into the habit of following only some of them, say when you're not under deadline pressure, and still pretend that you're an XP shop.

I would have liked more real-life stories in this book, in order to spice it up a little. As it is, everything that is there sounds highly reasonable (at least to me) but it wouldn't convince anyone who is skeptic of XP's supposed benefits. The example at the end of the book sounds contrived and hollow.

On the other hand, if you have been already convinced by Kent Beck's white book and want to start adopting XP, I can heartily recommend Mike Cohn's book.