--- product_id: 4804534 title: "Succeeding with Agile" brand: "mike cohn" price: "฿3410" currency: THB in_stock: true reviews_count: 13 url: https://www.desertcart.co.th/products/4804534-succeeding-with-agile store_origin: TH region: Thailand --- # Succeeding with Agile **Brand:** mike cohn **Price:** ฿3410 **Availability:** ✅ In Stock ## Quick Answers - **What is this?** Succeeding with Agile by mike cohn - **How much does it cost?** ฿3410 with free shipping - **Is it available?** Yes, in stock and ready to ship - **Where can I buy it?** [www.desertcart.co.th](https://www.desertcart.co.th/products/4804534-succeeding-with-agile) ## Best For - mike cohn enthusiasts ## Why This Product - Trusted mike cohn brand quality - Free international shipping included - Worldwide delivery with tracking - 15-day hassle-free returns ## Description Proven, 100% Practical Guidance for Making Scrum and Agile Work in Any Organization This is the definitive, realistic, actionable guide to starting fast with Scrum and agile–and then succeeding over the long haul. Leading agile consultant and practitioner Mike Cohn presents detailed recommendations, powerful tips, and real-world case studies drawn from his unparalleled experience helping hundreds of software organizations make Scrum and agile work. Succeeding with Agile is for pragmatic software professionals who want real answers to the most difficult challenges they face in implementing Scrum. Cohn covers every facet of the transition: getting started, helping individuals transition to new roles, structuring teams, scaling up, working with a distributed team, and finally, implementing effective metrics and continuous improvement. Throughout, Cohn presents “Things to Try Now” sections based on his most successful advice. Complementary “Objection” sections reproduce typical conversations with those resisting change and offer practical guidance for addressing their concerns. Coverage includes Practical ways to get started immediately–and “get good” fast Overcoming individual resistance to the changes Scrum requires Staffing Scrum projects and building effective teams Establishing “improvement communities” of people who are passionate about driving change Choosing which agile technical practices to use or experiment with Leading self-organizing teams Making the most of Scrum sprints, planning, and quality techniques Scaling Scrum to distributed, multiteam projects Using Scrum on projects with complex sequential processes or challenging compliance and governance requirements Understanding Scrum’s impact on HR, facilities, and project management Whether you've completed a few sprints or multiple agile projects and whatever your role–manager, developer, coach, ScrumMaster, product owner, analyst, team lead, or project lead–this book will help you succeed with your very next project. Then, it will help you go much further: It will help you transform your entire development organization. ## Technical Specifications | Specification | Value | |---------------|-------| | Dimensions | 7.4 x 0.79 x 9.09 inches | | Edition | 1st | | Isbn 10 | 0321579364 | | Isbn 13 | 978-0321579362 | | Item Weight | 1.8 pounds | | Language | English | | Part Of Series | Addison-Wesley Signature Series (Cohn) | | Print Length | 512 pages | | Publication Date | October 26, 2009 | | Publisher | Addison-Wesley Professional | ## Images ![Succeeding with Agile - Image 1](https://m.media-amazon.com/images/I/619HtJxffBL.jpg) ## Available Options This product comes in different **Format** options. ## Customer Reviews ### ⭐⭐⭐⭐⭐ A good book for solving the problems you may encounter while using Scrum. *by on Reviewed in the United States December 28, 2012* I recommend this book to those who are trying to spread Scrum into an organization.In the introduction to the book Mike Cohn states that the book is not for those new to Scrum or for purists. He says it is for those who have started Scrum and have run into problems.The book is divided into 5 parts:Part I Getting StartedPart II IndividualsPart III TeamsPart IV The OrganizationPart V Next Steps.Succeeding with Agile walks you through how to spread Scrum in your organization and how to get better at Scrum along the way.The author points out that being successful at rolling out Scrum can be difficult:"But there are certain attributes of transitioning to Scrum that make it more difficult than most other changes. They are as follows:* Successful change is not entirely top-down or bottom-up.* The end state is unpredictable.* Scrum is pervasive.* Scrum is dramatically different.* Change is coming more quickly than ever before.* Best practices are dangerous."Cohn also points out that departments outside of Engineering may have issues with Scrum:"Finance groups will have to reconcile company policies on capitalizing or expensing with the way Scrum projects run. Sales will want to consider altering how they communicate date and scope commitments and may change how they structure contracts. With more groups affected by a move to Scrum, there is more chance for resistance and certainly more chance for misunderstandings. These add up to make transitioning to Scrum harder than other changes."But for all of the difficulties, Scrum is very popular with stakeholders. Cohn says:"One reason stakeholders are so satisfied is that time-to-market is reduced when using an agile process like Scrum. This faster time-to-market is enabled by the higher productivity of agile teams, which is in turn the result of the higher quality seen on agile projects. Because employees are freed up to do high-quality work and because they see their work delivered sooner into the hands of waiting users, job satisfaction goes up. With higher job satisfaction comes more engaged employees, which leads to more productivity gains, initiating a virtuous cycle of continued improvement."Many organizations try to keep the role of Project Manager while also using Scrum. In the book, Mike Cohn argues against that:"On Scrum projects we acknowledge the untenable role of the project manager and eliminate it. Eliminating the role, though, does not mean we can do away with the work and responsibilities."He says that the responsibilities that were carried out by the Project Manager are shifted to the Team, the ScrumMaster and the Product Owner.The author notes that while the Scrum framework does not prescribe software development methodologies, Scrum teams have found certain practices improve the product. He writes:"...we will look at common technical practices used by Scrum teams to improve the quality of their work: test-driven development, refactoring, collective ownership, continuous integration, and pair programming. While I just referred to these as common practices, the truth is that they are not so common. These practices are well regarded and lead to higher quality, but because they can be hard to put into practice, they are used less often than they should be."Cohn also points out that planning is just as essential in Scrum as it is in other methodologies. He says:"Planning is a fundamental aspect of Scrum. Scrum teams commit to always working on the features with the highest value. To do this, the team and product owner must have an estimate of how much a feature will cost to develop; otherwise they are prioritizing on desirability alone. Similarly, it is important to estimate how long a feature will take to develop--a feature that misses a critical market window will deliver much less value. Clearly, for a Scrum team to live up to its promise of working in priority order, planning must be an essential practice."However, he points out that planning is not a one time acivity but is an ongoing one, where the plans are continually revised.Cohn also warns against trying to achieve quality by testing after the fact:"Scrum teams make testing a central practice and part of the development process rather than something that happens after the developers are 'done.' Rather than trying to test quality after a product has been built, we build quality into the process and product as it is being developed. W. Edwards Deming was an American professor and consultant best known for his work in Japan emphasizing the impact of quality on cost and productivity. He maintained that quality could not be added to a product later. He wrote that we should 'cease dependence on mass inspection to achieve quality. Improve the process and build quality into the product in the first place' (2000, 23)."Overall I learned a great deal from the book and enjoyed reading it. ### ⭐⭐⭐⭐⭐ The most practical guide to agile available *by on Reviewed in the United States May 16, 2010* Mike Cohn continues in his tradition of writing some of the most practical books available in the agile environment. His vast experience is evident in his approach to presenting the many questions practitioners and newcomers alike consider as they move ahead with agile practices. Without being dogmatic he provides the pros and cons of the issues at hand, helping to understand why one approach might be more desirable than another. As one example, in presenting the difference between feature teams and component teams, it would have been very easy (and overly simplistic) for Mike to indicate that feature teams are the way to go. Instead, he acknowledges that feature teams are strongly recommended, but that component team might be the right choice in some situations, and he explains what those situations might be.This book also makes a great reference. Have a question about the role Human Resources play in an agile environment? Look it up in the index and get some pertinent information without a lot of wading through other non-related material.The littering of "Objection" and "Things To Try Now" notes again add some very practical applications, both in dealing with common obstacles encountered while implementing agile practices, and also in recommending ways to move the cause forward without a lot of fuss.One very minor style critique: while I appreciate the extensive use of supporting reference material, the manner in which these are inserted into the book can be just a bit tiresome, almost giving a feeling of reading a research paper. I'm not sure that there's any way around this, and there's no contest between getting the supporting references vs. losing some of that to attain a style objective: the extra detail wins hands down.As an indication of the overall quality of "Succeeding With Agile" we have decided at Winnow Management to now use this book as our primary recommended reading to our clients. Great work, Mike! ### ⭐⭐⭐⭐ Per aspera ad astra *by on Reviewed in the United States January 3, 2011* After reading this book I have emerged with a split personality of Dr. Jekyll and Mr. Hyde. The Agile methodology as presented by Mr. Cohn contains a very valuable information based on his personal experience that can be utilized on many development projects and is written in a very light, easy to read language that will not make you tired after reading 15 pages. However it also contains extreme simplifications that makes me wonder whether Mr. Cohn is trying to sell Agile a little too hard. In too many cases my own experience (20 years in PM and total 27 years in software development) goes against many examples presented in the book.Let me pickup just one few example from the book.Mr. Cohn makes the case (page 237) that "With written document we do not iterate over the meaning as we would in conversation".Written documentation is a living document which captures all conversation we had with our company sale people, with customer (as customer business people and end users who are people that will use the system for their daily work) that is the basis for user acceptance test. Such document does not have to be developed 100% before starting implementation but needs to be 100% created and approved (signed off by customer) long before you finish the last line of code.Verbal conversations capture a lot of details that need to be separated into reality and customer dreams. Try to go to the court of law and resolve these differences based on conversations ( or loose documentation) that took place over many days with many people.I will not go over the issue with defining folder length ( on the same page 237) which made me laugh and cry at the same time. It is example of poor definition and not the example of why we need less documentation. This book has many rather childish examples like this one (see booking hotel on page 236) promoting Agile when Agile can stand on its own rather well).Final thought: If you are seriously considering diving into the world of Agile development, you should read this book, no question about it.I believe that this book is worth the price, it is worth to spend time reading but be aware that like all software development methodologies is not a silver bullet and it is a bag of new, interesting ideas and a lot of ideas that might have limited application in your environment. So "improvise and overcome" (Heartbreak Ridge, Sergeant Thomas Highway). ## Frequently Bought Together - Succeeding with Agile: Software Development Using Scrum - User Stories Applied: For Agile Software Development - Agile Estimating and Planning --- ## 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.co.th/products/4804534-succeeding-with-agile](https://www.desertcart.co.th/products/4804534-succeeding-with-agile) --- *Product available on Desertcart Thailand* *Store origin: TH* *Last updated: 2026-10-15*