- Paperback: 304 pages
- Publisher: Addison-Wesley Professional; 1 edition (March 11, 2004)
- Language: English
- ISBN-10: 0321205685
- ISBN-13: 978-0321205681
- Product Dimensions: 7 x 0.8 x 9.2 inches
- Shipping Weight: 1 pounds (View shipping rates and policies)
- Average Customer Review: 107 customer reviews
- Amazon Best Sellers Rank: #37,891 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
User Stories Applied: For Agile Software Development 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Fulfillment by Amazon (FBA) is a service we offer sellers that lets them store their products in Amazon's fulfillment centers, and we directly pack, ship, and provide customer service for these products. Something we hope you'll especially enjoy: FBA items qualify for FREE Shipping and Amazon Prime.
If you're a seller, Fulfillment by Amazon can help you increase your sales. We invite you to learn more about Fulfillment by Amazon .
Frequently bought together
Customers who bought this item also bought
Customers who viewed this item also viewed
From the Back Cover
Agile requirements: discovering what your users really want. With this book, you will learn to:
- Flexible, quick and practical requirements that work
- Save time and develop better software that meets users' needs
- Gathering user stories -- even when you can't talk to users
- How user stories work, and how they differ from use cases, scenarios, and traditional requirements
- Leveraging user stories as part of planning, scheduling, estimating, and testing
- Ideal 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 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.
Boston, MA 02116
About the Author
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).
Author interviews, book reviews, editors picks, and more. Read it now
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
Of all the risks in any software development project, the most dangerous (possibly fatal) risk is not bad code or incomplete tests - it is getting the requirements wrong. The impact can be anywhere from highly dissatisfied clients to unemployed development teams.
One of biggest advantages of Agile development is that it directly addresses the reality of changing system requirements and how to keep a project aimed directly for the key business goal even in such a fluid environment. User Stories, and how they are used in an Agile Project Management context, are a key tool in ensuring project success (AKA client satisfaction).
Project Managers, Scrum Masters, Lead Developers, QA and Test Leads, Product Owners as well as Business Analysts should read this text. So much of software development process thinking has to do with "doing the thing, in right manner" (AKA good system-building technique). This book covers "doing the right thing" (AKA building the right product).
The key-idea of user stories is that conversations and understanding via documentation is often wasteful and inefficient. User Stories describes a requirement in such a way that we can remember it in the future. At the time the requirement is ready to be implemented, we'll discuss the requirement in more detail. That way we can delay some of the requirement analysis and move it closer to when we implement it. This reduces "requirement inventory" and can lead to less waste in the development process. Whether and how to use user stories in your project depends on many different variables and user stories explained will explain the details of user stories, the different types of user stories and give plenty of examples. All this is needed for a better understanding and for deciding how user stories can help you on your project.
The book is well written, though personally I found that it contained too much text. There was quite much repetition and that made the book slightly boring after a 100 pages. It could have been written with less text, in my opinion. Another drawback of the book was that the examples given didn't feel real enough. It would have been nice to cover some larger projects and also discuss how user stories would work on these.
In conclusion, User Stories Applied is the definitive and only reference on user stories and when interested in user stories or when working with user stories, this is an absolute must!
This is by far the most lucid, well-written, practical book on the subject. Agile books tend to sometimes get too anecdotal and speak in metaphors before they give you some useful practical steps. Not this one.
Mr. Cohn starts being useful right away and gives practical and useful advice. This book was worth every penny. In fact it made the other books I read clearer.
If you want a simple effective explanation of how to write user stories, look no further.
It details the basics of interviewing, clarifying and capturing users' requirements in a true agile fashion.
The book then proceeds with describing the necessary interaction between the development team and the users / users' representatives (expert domains). Great job in providing a succinct analysis of the differences between the User Stories methodology and the IEEE software specifications as well as the Use Case technique.
Excellent examples accompany the theory.
The only problem is that User Stories is only a part (albeit an important one) in the Agile Methodology. The writer realizes the need to provide the basic principles of Agile but this part feels like a half baked effort to grow the book into something bigger than initially planned.