- Used Books
- Staff Picks
- Gifts & Gift Cards
- Sell Books
- Stores & Events
- Let's Talk Books
Special Offers see all
More at Powell's
Recently Viewed clear list
This item may be
Check for Availability
User Stories Applied: For Agile Software Developmentby Mike Cohn
Synopses & Reviews
This is the eBook version of the printed book.
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 proxiesWriting 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.
Boston, MA 02116
The concept of user stories has its roots as one of the main tenets of Extreme Programming. In simple terms, user stories represent an effective means of gathering requirements from the customer (roughly akin to use cases). This book describes user stories and demonstrates how they can be used to properly plan, manage, and test software development projects. The book highlights both successful and unsuccessful implementations of the concept, and provides sets of questions and exercises that drive home its main points. After absorbing the lessons in this book, readers will be able to introduce user stories in their organizations as an effective means of determining precisely what is required of a software application.
Table of Contents
Foreword — Acknowledgments — Introduction — I:An Overview / GETTING STARTED. 1 — 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 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 — ESTIMATING A / II.
What Our Readers Are Saying