User Stories Applied: For Agile Software Development

Note: Supplemental materials are not guaranteed with Rental or Used book purchases.

ISBN: 9780321205681 | 0321205685
Cover: Paperback
Copyright: 3/1/2004

Rent

(Recommended)

$51.12

Term

Due

Price

Semester

Dec 11

$51.12

*This item is part of an exclusive publisher rental program and requires an additional convenience fee. This fee will be reflected in the shopping bag.
Buy New

In Stock Usually Ships in 24 Hours.

$54.39
eBook

Available Instantly

Lifetime Access

*To support the delivery of the digital material to you, a digital delivery fee of $3.99 will be charged on each digital item.

$63.59*

Supplemental Materials

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.

Foreword	p. xv
Acknowledgments	p. xvii
Introduction	p. xix
Getting Started	p. 1
An Overview	p. 3
What Is a User Story?	p. 4
Where Are the Details?	p. 5
"How Long Does It Have to Be?"	p. 7
The Customer Team	p. 8
What Will the Process Be Like?	p. 8
Planning Releases and Iterations	p. 10
What Are Acceptance Tests?	p. 12
Why Change?	p. 13
Summary	p. 15
Questions	p. 15
Writing Stories	p. 17
Independent	p. 17
Negotiable	p. 18
Valuable to Purchasers or Users	p. 20
Estimatable	p. 22
Small	p. 23
Testable	p. 27
Summary	p. 28
Developer Responsibilities	p. 28
Customer Responsibilities	p. 28
Questions	p. 29
User Role Modeling	p. 31
User Roles	p. 31
Role Modeling Steps	p. 33
Two Additional Techniques	p. 37
What If I Have On-Site Users?	p. 39
Summary	p. 40
Developer Responsibilities	p. 40
Customer Responsibilities	p. 41
Questions	p. 41
Gathering Stories	p. 43
Elicitation and Capture Should Be Illicit	p. 43
A Little Is Enough, or Is It?	p. 44
Techniques	p. 45
User Interviews	p. 45
Questionnaires	p. 47
Observation	p. 48
Story-Writing Workshops	p. 49
Summary	p. 52
Developer Responsibilities	p. 53
Customer Responsibilities	p. 53
Questions	p. 53
Working with User Proxies	p. 55
The Users' Manager	p. 55
A Development Manager	p. 57
Salespersons	p. 57
Domain Experts	p. 58
The Marketing Group	p. 59
Former Users	p. 59
Customers	p. 59
Trainers and Technical Support	p. 61
Business or Systems Analysts	p. 61
What to Do When Working with a User Proxy	p. 61
Can You Do It Yourself?	p. 63
Constituting the Customer Team	p. 63
Summary	p. 64
Developer Responsibilities	p. 65
Customer Responsibilities	p. 65
Questions	p. 66
Acceptance Testing User Stories	p. 67
Write Tests Before Coding	p. 68
The Customer Specifies the Tests	p. 69
Testing Is Part of the Process	p. 69
How Many Tests Are Too Many?	p. 70
The Framework for Integrated Test	p. 70
Types of Testing	p. 72
Summary	p. 73
Developer Responsibilities	p. 73
Customer Responsibilities	p. 73
Questions	p. 74
Guidelines for Good Stories	p. 75
Start with Goal Stories	p. 75
Slice the Cake	p. 75
Write Closed Stories	p. 76
Put Constraints on Cards	p. 77
Size the Story to the Horizon	p. 78
Keep the UI Out as Long as Possible	p. 79
Some Things Aren't Stories	p. 80
Include User Roles in the Stories	p. 80
Write for One User	p. 81
Write in Active Voice	p. 81
Customer Writes	p. 81
Don't Number Story Cards	p. 82
Don't Forget the Purpose	p. 82
Summary	p. 82
Questions	p. 83
Estimating and Planning	p. 85
Estimating User Stories	p. 87
Story Points	p. 87
Estimate as a Team	p. 88
Estimating	p. 88
Triangulate	p. 90
Using Story Points	p. 91
What If We Pair Program?	p. 92
Some Reminders	p. 93
Summary	p. 94
Developer Responsibilities	p. 94
Customer Responsibilities	p. 95
Questions	p. 95
Planning a Release	p. 97
When Do We Want the Release?	p. 98
What Would You Like in It?	p. 98
Prioritizing the Stories	p. 99
Mixed Priorities	p. 100
Risky Stories	p. 101
Prioritizing Infrastructural Needs	p. 101
Selecting an Iteration Length	p. 103
From Story Points to Expected Duration	p. 103
The Initial Velocity	p. 104
Creating the Release Plan	p. 105
Summary	p. 106
Developer Responsibilities	p. 106
Customer Responsibilities	p. 107
Questions	p. 107
Planning an Iteration	p. 109
Iteration Planning Overview	p. 109
Discussing the Stories	p. 110
Disaggregating into Tasks	p. 111
Accepting Responsibility	p. 113
Estimate and Confirm	p. 113
Summary	p. 115
Developer Responsibilities	p. 115
Customer Responsibilities	p. 116
Questions	p. 116
Measuring and Monitoring Velocity	p. 117
Measuring Velocity	p. 117
Planned and Actual Velocity	p. 119
Iteration Burndown Charts	p. 121
Burndown Charts During an Iteration	p. 123
Summary	p. 126
Developer Responsibilities	p. 127
Customer Responsibilities	p. 127
Questions	p. 127
Frequently Discussed Topics	p. 131
What Stories Are Not	p. 133
User Stories Aren't IEEE 830	p. 133
User Stories Are Not Use Cases	p. 137
User Stories Aren't Scenarios	p. 141
Summary	p. 143
Questions	p. 143
Why User Stories?	p. 145
Verbal Communication	p. 145
User Stories Are Comprehensible	p. 148
User Stories Are the Right Size for Planning	p. 148
User Stories Work for Iterative Development	p. 149
Stories Encourage Deferring Detail	p. 150
Stories Support Opportunistic Development	p. 151
User Stories Encourage Participatory Design	p. 152
Stories Build Up Tacit Knowledge	p. 153
Why Not Stories?	p. 153
Summary	p. 154
Developer Responsibilities	p. 155
Customer Responsibilities	p. 155
Questions	p. 155
A Catalog of Story Smells	p. 157
Stories Are Too Small	p. 157
Interdependent Stories	p. 157
Goldplating	p. 158
Too Many Details	p. 159
Including User Interface Detail Too Soon	p. 159
Thinking Too Far Ahead	p. 160
Splitting Too Many Stories	p. 160
Customer Has Trouble Prioritizing	p. 161
Customer Won't Write and Prioritize the Stories	p. 162
Summary	p. 162
Developer Responsibilities	p. 163
Customer Responsibilities	p. 163
Questions	p. 163
Using Stories with Scrum	p. 165
Scrum Is Iterative and Incremental	p. 165
The Basics of Scrum	p. 166
The Scrum Team	p. 166
The Product Backlog	p. 167
The Sprint Planning Meeting	p. 168
The Sprint Review Meeting	p. 170
The Daily Scrum Meeting	p. 171
Adding Stories to Scrum	p. 173
A Case Study	p. 174
Summary	p. 175
Questions	p. 176
Additional Topics	p. 177
Handling NonFunctional Requirements	p. 177
Paper or Software?	p. 179
User Stories and the User Interface	p. 181
Retaining the Stories	p. 184
Stories for Bugs	p. 185
Summary	p. 186
Developer Responsibilities	p. 186
Customer Responsibilities	p. 187
Questions	p. 187
An Example	p. 189
The User Roles	p. 191
The Project	p. 191
Identifying the Customer	p. 191
Identifying Some Initial Roles	p. 192
Consolidating and Narrowing	p. 193
Role Modeling	p. 195
Adding Personas	p. 197
The Stories	p. 199
Stories for Teresa	p. 199
Stories for Captain Ron	p. 202
Stories for a Novice Sailor	p. 203
Stories for a Non-Sailing Gift Buyer	p. 204
Stories for a Report Viewer	p. 204
Some Administration Stories	p. 205
Wrapping Up	p. 206
Estimating the Stories	p. 209
The First Story	p. 210
Advanced Search	p. 212
Rating and Reviewing	p. 213
Accounts	p. 214
Finishing the Estimates	p. 215
All the Estimates	p. 216
The Release Plan	p. 219
Estimating Velocity	p. 219
Prioritizing the Stories	p. 220
The Finished Release Plan	p. 221
The Acceptance Tests	p. 223
The Search Tests	p. 223
Shopping Cart Tests	p. 224
Buying Books	p. 225
User Accounts	p. 226
Administration	p. 227
Testing the Constraints	p. 228
A Final Story	p. 229
Appendices	p. 231
An Overview of Extreme Programming	p. 233
Roles	p. 233
The Twelve Practices	p. 234
XP's Values	p. 240
The Principles of XP	p. 241
Summary	p. 242
Answers to Questions	p. 245
Chapter 1, An Overview	p. 245
Chapter 2, Writing Stories	p. 246
Chapter 3, User Role Modeling	p. 247
Chapter 4, Gathering Stories	p. 248
Chapter 5, Working with User Proxies	p. 249
Chapter 6, Acceptance Testing User Stories	p. 249
Chapter 7, Guidelines for Good Stories	p. 249
Chapter 8, Estimating User Stories	p. 251
Chapter 9, Planning a Release	p. 251
Chapter 10, Planning an Iteration	p. 252
Chapter 11, Measuring and Monitoring Velocity	p. 252
Chapter 12, What Stories Are Not	p. 253
Chapter 13, Why User Stories?	p. 254
Chapter 14, A Catalog of Story Smells	p. 255
Chapter 15, Using Stories with Scrum	p. 255
Chapter 16, Additional Topics	p. 256
References	p. 259
Index	p. 263
Table of Contents provided by Ingram. All Rights Reserved.

FREE SHIPPING

Rent More, Save More! Use code: BBRENTAL

5% off 1 book, 7% off 2 books, 10% off 3+ books

User Stories Applied: For Agile Software Development

Summary

Author Biography

Table of Contents

Supplemental Materials