--- product_id: 3700797 title: "User Stories Applied: For Agile Software Development (Addison-Wesley Signature Series (Beck))" price: "270 zł" currency: PLN in_stock: true reviews_count: 8 url: https://www.desertcart.pl/products/3700797-user-stories-applied-for-agile-software-development-addison-wesley-signature store_origin: PL region: Poland --- # User Stories Applied: For Agile Software Development (Addison-Wesley Signature Series (Beck)) **Price:** 270 zł **Availability:** ✅ In Stock ## Quick Answers - **What is this?** User Stories Applied: For Agile Software Development (Addison-Wesley Signature Series (Beck)) - **How much does it cost?** 270 zł with free shipping - **Is it available?** Yes, in stock and ready to ship - **Where can I buy it?** [www.desertcart.pl](https://www.desertcart.pl/products/3700797-user-stories-applied-for-agile-software-development-addison-wesley-signature) ## Best For - Customers looking for quality international products ## Why This Product - Free international shipping included - Worldwide delivery with tracking - 15-day hassle-free returns ## Description User Stories Applied: For Agile Software Development (Addison-Wesley Signature Series (Beck)) [Cohn, Mike] on desertcart.com. *FREE* shipping on qualifying offers. User Stories Applied: For Agile Software Development (Addison-Wesley Signature Series (Beck)) Review: Finally! Practical advice on writing user stories, and more - This excellent book is a must-have for anyone on an agile team - developers, testers, business experts, analysts - and for anyone who struggles with requirements, planning, or estimating on any software project. User Stories Applied is easy to read and digest. As the title suggests, its techniques are easy to apply and deliver huge value. Each chapter summarizes developer and customer responsibilities, and has questions whose answers are provided in an appendix. The book is full of real-life, concrete examples, allowing you to learn from the successes and failures of others. This book will give you many tools to help your projects succeed. Just a few of the most valuable topics: When are user stories too big, too small, too detailed, too general, too open ended, when are they not user stories, and how to correct all these. Why use user stories. How to handle requirements for infrastructure, performance, qualitative aspects, UI. How to ask questions to elicit requirements. How to cope when you don't have `on-site customers'. Practical ways to estimate stories. Monitoring velocity and progress. When to keep and when to discard artifacts. Mike explores the differences between stories and other techniques for delivering requirements: IEEE 380, use cases, scenarios. He points out many positive side effects of user stories, such as encouraging participatory design and tacit knowledge accumulation. I particularly like that the book emphasizes the team's responsibility to successfully complete each iteration. I enjoy Mike's illuminating bits of wisdom, such as the "everything takes 4 hours" example. I love the comprehensive example in Part IV. No matter what your level of experience, you'll put the ideas in this book to immediate and productive use. Review: Outstanding text that is easy to read and understand. - Mike Cohn's clear and digestible writing style makes him my favorite Agile author. This book continues that tradition. 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). ## Technical Specifications | Specification | Value | |---------------|-------| | Best Sellers Rank | #338,735 in Books ( See Top 100 in Books ) #63 in Software Design & Engineering #323 in Software Development (Books) #813 in Computer Software (Books) | | Customer Reviews | 4.6 4.6 out of 5 stars (594) | | Dimensions | 7 x 0.67 x 9.25 inches | | Edition | 1st | | ISBN-10 | 0321205685 | | ISBN-13 | 978-0321205681 | | Item Weight | 1.1 pounds | | Language | English | | Part of series | Addison-Wesley Signature Series (Beck) | | Print length | 296 pages | | Publication date | March 1, 2004 | | Publisher | Addison-Wesley Professional | ## Images ![User Stories Applied: For Agile Software Development (Addison-Wesley Signature Series (Beck)) - Image 1](https://m.media-amazon.com/images/I/61Q4N2wfIRL.jpg) ![User Stories Applied: For Agile Software Development (Addison-Wesley Signature Series (Beck)) - Image 2](https://m.media-amazon.com/images/I/61rO3lZ2AlL.jpg) ![User Stories Applied: For Agile Software Development (Addison-Wesley Signature Series (Beck)) - Image 3](https://m.media-amazon.com/images/I/31IbmJWe3gL.jpg) ## Customer Reviews ### ⭐⭐⭐⭐⭐ Finally! Practical advice on writing user stories, and more *by L***N on March 14, 2004* This excellent book is a must-have for anyone on an agile team - developers, testers, business experts, analysts - and for anyone who struggles with requirements, planning, or estimating on any software project. User Stories Applied is easy to read and digest. As the title suggests, its techniques are easy to apply and deliver huge value. Each chapter summarizes developer and customer responsibilities, and has questions whose answers are provided in an appendix. The book is full of real-life, concrete examples, allowing you to learn from the successes and failures of others. This book will give you many tools to help your projects succeed. Just a few of the most valuable topics: When are user stories too big, too small, too detailed, too general, too open ended, when are they not user stories, and how to correct all these. Why use user stories. How to handle requirements for infrastructure, performance, qualitative aspects, UI. How to ask questions to elicit requirements. How to cope when you don't have `on-site customers'. Practical ways to estimate stories. Monitoring velocity and progress. When to keep and when to discard artifacts. Mike explores the differences between stories and other techniques for delivering requirements: IEEE 380, use cases, scenarios. He points out many positive side effects of user stories, such as encouraging participatory design and tacit knowledge accumulation. I particularly like that the book emphasizes the team's responsibility to successfully complete each iteration. I enjoy Mike's illuminating bits of wisdom, such as the "everything takes 4 hours" example. I love the comprehensive example in Part IV. No matter what your level of experience, you'll put the ideas in this book to immediate and productive use. ### ⭐⭐⭐⭐⭐ Outstanding text that is easy to read and understand. *by A***R on February 5, 2014* Mike Cohn's clear and digestible writing style makes him my favorite Agile author. This book continues that tradition. 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 definitive reference on User Stories *by B***E on December 10, 2006* User stories are a method of capturing requirements which was originally introduced in the extreme programming method. User stories are commonly described as "a promiss for a conversation" and are often recorded on index cards (at least, originally). Mike Cohn's book takes the user story practice out of Extreme Programming and shows how it can be used in general in different methods. 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! ## Frequently Bought Together - User Stories Applied: For Agile Software Development - Agile Estimating and Planning - Succeeding with Agile: Software Development Using Scrum --- ## Why Shop on Desertcart? - 🛒 **Trusted by 1.3+ Million Shoppers** — Serving international shoppers since 2016 - 🌍 **Shop Globally** — Access 737+ million products across 21 categories - 💰 **No Hidden Fees** — All customs, duties, and taxes included in the price - 🔄 **15-Day Free Returns** — Hassle-free returns (30 days for PRO members) - 🔒 **Secure Payments** — Trusted payment options with buyer protection - ⭐ **TrustPilot Rated 4.5/5** — Based on 8,000+ happy customer reviews **Shop now:** [https://www.desertcart.pl/products/3700797-user-stories-applied-for-agile-software-development-addison-wesley-signature](https://www.desertcart.pl/products/3700797-user-stories-applied-for-agile-software-development-addison-wesley-signature) --- *Product available on Desertcart Poland* *Store origin: PL* *Last updated: 2026-05-24*