Home > Store

User Stories Applied: For Agile Software Development

Register your product to gain access to bonus material or receive a coupon.

User Stories Applied: For Agile Software Development

Best Value Purchase

Book + eBook Bundle

  • Your Price: $59.39
  • List Price: $98.98
  • Includes EPUB, MOBI, and PDF
  • About eBook Formats
  • This eBook includes the following formats, accessible from your Account page after purchase:

    ePub EPUB The open industry format known for its reflowable content and usability on supported mobile devices.

    MOBI MOBI The eBook format compatible with the Amazon Kindle and Amazon Kindle applications.

    Adobe Reader PDF The popular standard, used most often with the free Adobe® Reader® software.

    This eBook requires no passwords or activation to read. We customize your eBook by discreetly watermarking it with your name, making it uniquely yours.

More Purchase Options

Book

  • Your Price: $43.99
  • List Price: $54.99
  • Usually ships in 24 hours.

eBook (Watermarked)

  • Your Price: $35.19
  • List Price: $43.99
  • Includes EPUB, MOBI, and PDF
  • About eBook Formats
  • This eBook includes the following formats, accessible from your Account page after purchase:

    ePub EPUB The open industry format known for its reflowable content and usability on supported mobile devices.

    MOBI MOBI The eBook format compatible with the Amazon Kindle and Amazon Kindle applications.

    Adobe Reader PDF The popular standard, used most often with the free Adobe® Reader® software.

    This eBook requires no passwords or activation to read. We customize your eBook by discreetly watermarking it with your name, making it uniquely yours.

About

Features

Learn to build robust software that more closely meets the customer's needs through applying the concept of user stories.

° A clear explanation of the most agile means of gathering software requirements

° Thoroughly reviewed and eagerly anticipated by the agile software development community

° Allows the reader to save time and resources by gathering the proper requirements BEFORE coding begins

Description

  • Copyright 2004
  • Dimensions: 7" x 9-1/4"
  • Pages: 304
  • Edition: 1st
  • Book
  • ISBN-10: 0-321-20568-5
  • ISBN-13: 978-0-321-20568-1

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.

Sample Content

Online Sample Chapter

Telling Stories and User Role Modeling

Sample Pages

Download the sample pages (includes Chapter 3 and Index)

Table of Contents



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.

Estimatable.

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

Updates

Submit Errata

More Information

Unlimited one-month access with your purchase
Free Safari Membership