User stories applied : for agile software development

Author

• Cohn, Mike

Additional Author(s)

-

Publisher

Boston: Addison-Wesley, 2004

Language

English

ISBN

9780321205681

Series

The Addison Wesley Signature series

Subject(s)

• AGILE SOFTWARE DEVELOPMENT

Notes

. Bibliography: p. 259-262. Index: p. 263-268

Abstract

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.

Physical Dimension

Number of Page(s)

xxii, 268 p.

Dimension

23 cm.

Other Desc.

-

Summary / Review / Table of Content

Foreword.
Acknowledgments.
Introduction.
I: GETTING STARTED.
1: An Overview.
What Is a User Story?
Where Are the Details?
"How Long Does It Have to Be?"
The Customer Team.
What Will the Process Be Like?
Planning Releases and Iterations.
What Are Acceptance Tests?
Why Change?
Summary.
Questions.
2: Writing Stories.
Independent.
Negotiable.
Valuable to Purchasers or Users.
Estimable.
Small.
Testable.
Summary.
Developer Responsibilities.
Customer Responsibilities.
Questions.
3: User Role Modeling.
User Roles.
Role Modeling Steps.
Two Additional Techniques.
What If I Have On-Site Users?
Summary.
Developer Responsibilities.
Customer Responsibilities.
Questions.
4: Gathering Stories.
Elicitation and Capture Should Be Illicit.
A Little Is Enough, or Is It?
Techniques.
User Interviews.
Questionnaires.
Observation.
Story-Writing Workshops.
Summary.
Developer Responsibilities.
Customer Responsibilities.
Questions.
5: Working with User Proxies.
The Users' Manager.
A Development Manager.
Salespersons.
Domain Experts.
The Marketing Group.
Former Users.
Customers.
Trainers and Technical Support.
Business or Systems Analysts.
What to Do When Working with a User Proxy.
Can You Do It Yourself?
Constituting the Customer Team.
Summary.
Developer Responsibilities.
Customer Responsibilities.
Questions.
6: Acceptance Testing User Stories.
Write Tests Before Coding.
The Customer Specifies the Tests.
Testing Is Part of the Process.
How Many Tests Are Too Many?
The Framework for Integrated Test.
Types of Testing. Summary.
Developer Responsibilities.
Customer Responsibilities.
Questions.
7: Guidelines for Good Stories.
Start with Goal Stories.
Slice the Cake.
Write Closed Stories.
Put Constraints on Cards.
Size the Story to the Horizon.
Keep the UI Out as Long as Possible.
Some Things Aren't Stories.
Include User Roles in the Stories.
Write for One User.
Write in Active Voice.
Customer Writes.
Don't Number Story Cards.
Don't Forget the Purpose.
Summary.
Questions.
II: ESTIMATING AND PLANNING.
8: Estimating User Stories.
Story Points.
Estimate as a Team.
Estimating.
Triangulate.
Using Story Points.
What If We Pair Program?
Some Reminders.
Summary.
Developer Responsibilities.
Customer Responsibilities.
Questions.
9: Planning a Release.
When Do We Want the Release?
What Would You Like in It?
Prioritizing the Stories.
Mixed Priorities.
Risky Stories.
Prioritizing Infrastructural Needs.
Selecting an Iteration Length.
From Story Points to Expected Duration.
The Initial Velocity.
Creating the Release Plan.
Summary.
Developer Responsibilities.
Customer Responsibilities.
Questions.
10: Planning an Iteration.
Iteration Planning Overview.
Discussing the Stories.
Disaggregating into Tasks.
Accepting Responsibility.
Estimate and Confirm.
Summary.
Developer Responsibilities.
Customer Responsibilities.
Questions.
11: Measuring and Monitoring Velocity.
Measuring Velocity.
Planned and Actual Velocity.
Iteration Burndown Charts.
Burndown Charts During an Iteration.
Summary.
Developer Res.

Exemplar(s)

#	Accession No.	Call Number	Location	Status
1.	03015/18	005.1 Coh U	Library - 7th Floor	Available