User Stories Applied: For Agile Software Development

Front Cover
Addison-Wesley Professional, 2004 - Computers - 268 pages
Agile requirements: discovering what your users really want. With this book, you will learn to:Flexible, quick and practical requirements that workSave time and develop better software that meets users' needsGathering user stories -- even when you can't talk to usersHow user stories work, and how they differ from use cases, scenarios, and traditional requirementsLeveraging user stories as part of planning, scheduling, estimating, and testingIdeal 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.
 

What people are saying - Write a review

User ratings

5 stars
9
4 stars
9
3 stars
5
2 stars
0
1 star
0

LibraryThing Review

User Review  - EmreSevinc - LibraryThing

This short book promises to explain what User Stories are, what they aren't, how to create and utilize them within an Agile/XP approach, and finally how to bring everything together in a short, yet ... Read full review

LibraryThing Review

User Review  - jrep - LibraryThing

Clear, readable, quick-moving yet substantive, this book combines a thorough introduction into the concept and uses of user stories, with insights into their strengths relative to similar or confusing tools like "use cases." Read full review

Contents

Getting Started
An Overview
Where Are the Details?
How Long Does It Have to Be?
The Customer Team
Planning Releases and Iterations
What Are Acceptance Tests?
Why Change?
Developer Responsibilities
Frequently Discussed Topics
What Stories Are Not
User Stories Are Not Use Cases
User Stories Arent Scenarios
Summary
Why User Stories?
User Stories Are Comprehensible

Summary
Writing Stories
Negotiable
Valuable to Purchasers or Users
Estimatable
Small
Testable
Summary
Questions
User Role Modeling
Role Modeling Steps
Two Additional Techniques
What If I Have OnSite Users?
Summary
Customer Responsibilities
Gathering Stories
A Little Is Enough or Is It?
Techniques
Questionnaires
Observation
StoryWriting Workshops
Summary
Developer Responsibilities
Working with User Proxies
A Development Manager
Domain Experts
The Marketing Group
Trainers and Technical Support
Can You Do It Yourself?
Summary
Developer Responsibilities
Questions
Acceptance Testing User Stories
Write Tests Before Coding
The Customer Specifies the Tests
How Many Tests Are Too Many?
Types of Testing
Summary
Questions
Guidelines for Good Stories
Write Closed Stories
Put Constraints on Cards
Size the Story to the Horizon
Keep the UI Out as Long as Possible
Some Things Arent Stories
Write for One User
Dont Number Story Cards
Questions
Estimating and Planning
Estimating User Stories
Using Story Points
What If We Pair Program?
Some Reminders
Summary
Customer Responsibilities
Planning a Release
When Do We Want the Release?
Prioritizing the Stories
Risky Stories
Selecting an Iteration Length
The Initial Velocity
Creating the Release Plan
Summary
Customer Responsibilities
Planning an Iteration
Discussing the Stories
Disaggregating into Tasks
Accepting Responsibility
Summary
Customer Responsibilities
Measuring and Monitoring Velocity
Planned and Actual Velocity
Iteration Burndown Charts
Burndown Charts During an Iteration
Summary
User Stories Work for Iterative Development
Stories Encourage Deferring Detail
Stories Support Opportunistic Development
User Stories Encourage Participatory Design
Stories Build Up Tacit Knowledge
Summary
Developer Responsibilities
A Catalog of Story Smells
Goldplating
Too Many Details
Customer Has Trouble Prioritizing
Customer Wont Write and Prioritize the Stories
Developer Responsibilities
Using Stories with Scrum
The Basics of Scrum
The Product Backlog
The Sprint Review Meeting
The Daily Scrum Meeting
Adding Stories to Scrum
A Case Study
Summary
Questions
Additional Topics
Paper or Software?
User Stories and the User Interface
Retaining the Stories
Stories for Bugs
Summary
Customer Responsibilities
An Example
The User Roles
Consolidating and Narrowing
Role Modeling
Adding Personas
The Stories
Stories for Captain Ron
Stories for a Novice Sailor
Stories for a NonSailing Gift Buyer
Some Administration Stories
Wrapping Up
Estimating the Stories
The First Story
Rating and Reviewing
Accounts
Finishing the Estimates
All the Estimates
The Release Plan
Prioritizing the Stories
The Finished Release Plan
The Acceptance Tests
Shopping Cart Tests
Buying Books
User Accounts
Administration
Testing the Constraints
A Final Story
Appendices
An Overview of Extreme Programming
The Twelve Practices
XPs Values
The Principles of XP
Summary
Answers to Questions
Chapter 2 Writing Stories
Chapter 3 User Role Modeling
Chapter 5 Working with User Proxies
Chapter 8 Estimating User Stories
Chapter 10 Planning an Iteration
Chapter 12 What Stories Are Not
Chapter 13 Why User Stories?
Chapter 14 A Catalog of Story Smells
Chapter 16 Additional Topics
References
Index
Copyright

Other editions - View all

Common terms and phrases

About the author (2004)

Mike Cohn is the founder of Mountain Goat Software, a process and project management consultancy and training firm. With more than twenty years of experience, Mike has been a technology executive in companies ranging from start-ups to Fortune 40s, and is a founding member of the Agile Alliance. He frequently contributes to industry-related magazines and presents regularly at conferences. He is the author of User Stories Applied (Addison-Wesley, 2004).

Bibliographic information