User Stories Applied: For Agile Software Development

Front Cover
Addison-Wesley Professional, 2004 - Computers - 268 pages
62 Reviews

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.

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 workshopsWorking with managers, trainers, salespeople and other "proxies"Writing user stories for acceptance testing Using stories to prioritize, set schedules, and estimate release costsIncludes 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.

ADDISON-WESLEY PROFESSIONAL

Boston, MA 02116

www.awprofessional.com

ISBN: 0-321-20568-5

  

What people are saying - Write a review

User ratings

5 stars
22
4 stars
29
3 stars
10
2 stars
1
1 star
0

Interesting insights. - Goodreads
Good tips to fit User Stories with agile practices. - Goodreads
... the best intro to scrum ive read yet. - Goodreads

Review: User Stories Applied: For Agile Software Development

User Review  - Nestor Jimenez - Goodreads

Good tips to fit User Stories with agile practices. Read full review

Review: User Stories Applied: For Agile Software Development

User Review  - David - Goodreads

Very good read for a first time product owner. Read full review

Contents

Getting Started
1
An Overview
3
What Is a User Story?
4
Where Are the Details?
5
How Long Does It Have to Be?
7
The Customer Team
8
Planning Releases and Iterations
10
What Are Acceptance Tests?
12
Frequently Discussed Topics
131
What Stories Are Not
133
User Stories Are Not Use Cases
137
User Stories Arent Scenarios
141
Summary
143
Why User Stories?
145
User Stories Are Comprehensible
148
User Stories Work for Iterative Development
149

Why Change?
13
Summary
15
Writing Stories
17
Negotiable
18
Valuable to Purchasers or Users
20
Estimatable
22
Small
23
Testable
27
Summary
28
Questions
29
User Role Modeling
31
Role Modeling Steps
33
Two Additional Techniques
37
What If I Have OnSite Users?
39
Summary
40
Customer Responsibilities
41
Gathering Stories
43
A Little Is Enough or Is It?
44
Techniques
45
Questionnaires
47
Observation
48
StoryWriting Workshops
49
Summary
52
Developer Responsibilities
53
Working with User Proxies
55
A Development Manager
57
Domain Experts
58
The Marketing Group
59
Trainers and Technical Support
61
Can You Do It Yourself?
63
Summary
64
Developer Responsibilities
65
Questions
66
Acceptance Testing User Stories
67
Write Tests Before Coding
68
The Customer Specifies the Tests
69
How Many Tests Are Too Many?
70
Types of Testing
72
Summary
73
Questions
74
Guidelines for Good Stories
75
Write Closed Stories
76
Put Constraints on Cards
77
Size the Story to the Horizon
78
Keep the UI Out as Long as Possible
79
Some Things Arent Stories
80
Write for One User
81
Dont Number Story Cards
82
Questions
83
Estimating and Planning
85
Estimating User Stories
87
Estimate as a Team
88
Triangulate
90
Using Story Points
91
What If We Pair Program?
92
Some Reminders
93
Summary
94
Customer Responsibilities
95
Planning a Release
97
When Do We Want the Release?
98
Prioritizing the Stories
99
Mixed Priorities
100
Risky Stories
101
Selecting an Iteration Length
103
The Initial Velocity
104
Creating the Release Plan
105
Summary
106
Customer Responsibilities
107
Planning an Iteration
109
Discussing the Stories
110
Disaggregating into Tasks
111
Accepting Responsibility
113
Summary
115
Customer Responsibilities
116
Measuring and Monitoring Velocity
117
Planned and Actual Velocity
119
Iteration Burndown Charts
121
Burndown Charts During an Iteration
123
Summary
126
Developer Responsibilities
127
Stories Encourage Deferring Detail
150
Stories Support Opportunistic Development
151
User Stories Encourage Participatory Design
152
Stories Build Up Tacit Knowledge
153
Summary
154
Developer Responsibilities
155
A Catalog of Story Smells
157
Goldplating
158
Too Many Details
159
Thinking Too Far Ahead
160
Customer Has Trouble Prioritizing
161
Customer Wont Write and Prioritize the Stories
162
Developer Responsibilities
163
Using Stories with Scrum
165
The Basics of Scrum
166
The Product Backlog
167
The Sprint Planning Meeting
168
The Sprint Review Meeting
170
The Daily Scrum Meeting
171
Adding Stories to Scrum
173
A Case Study
174
Summary
175
Questions
176
Additional Topics
177
Paper or Software?
179
User Stories and the User Interface
181
Retaining the Stories
184
Stories for Bugs
185
Summary
186
Customer Responsibilities
187
An Example
189
The User Roles
191
Identifying Some Initial Roles
192
Consolidating and Narrowing
193
Role Modeling
195
Adding Personas
197
The Stories
199
Stories for Captain Ron
202
Stories for a Novice Sailor
203
Stories for a NonSailing Gift Buyer
204
Some Administration Stories
205
Wrapping Up
206
Estimating the Stories
209
The First Story
210
Advanced Search
212
Rating and Reviewing
213
Accounts
214
Finishing the Estimates
215
All the Estimates
216
The Release Plan
219
Prioritizing the Stories
220
The Finished Release Plan
221
The Acceptance Tests
223
Shopping Cart Tests
224
Buying Books
225
User Accounts
226
Administration
227
Testing the Constraints
228
A Final Story
229
Appendices
231
An Overview of Extreme Programming
233
The Twelve Practices
234
XPs Values
240
The Principles of XP
241
Summary
242
Answers to Questions
245
Chapter 2 Writing Stories
246
Chapter 3 User Role Modeling
247
Chapter 4 Gathering Stories
248
Chapter 5 Working with User Proxies
249
Chapter 8 Estimating User Stories
251
Chapter 10 Planning an Iteration
252
Chapter 12 What Stories Are Not
253
Chapter 13 Why User Stories?
254
Chapter 14 A Catalog of Story Smells
255
Chapter 16 Additional Topics
256
References
259
Index
263
Copyright

Common terms and phrases

Popular passages

Page 264 - Beck, Kent. Test-Driven Development. Reading, MA: Addison-Wesley, November 2002. Bloch, Joshua. Effective Java Programming Language Guide. Reading, MA : AddisonWesley, June 2001. Fowler, Martin, et al. Refactoring : Improving the Design of Existing Code. Reading, MA: Addison-Wesley, 1999. Gamma, Richard Helm, Ralph Johnson, and John Vlissides (The Gang of Four). Design Patterns : Elements of Reusable Object-Oriented Software. Reading, MA : Addison-Wesley, 1994. Hatcher, Erik, and...
Page 264 - Interaction Relabelling and Extreme Characters: Methods for exploring aesthetic interactions.

References to this book

All Book Search results »

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