--- product_id: 3700798 title: "Agile Estimating and Planning (Robert C. Martin Series)" price: "11136 som" currency: KGS in_stock: true reviews_count: 13 url: https://www.desertcart.kg/products/3700798-agile-estimating-and-planning-robert-c-martin-series store_origin: KG region: Kyrgyzstan --- # Agile Estimating and Planning (Robert C. Martin Series) **Price:** 11136 som **Availability:** ✅ In Stock ## Quick Answers - **What is this?** Agile Estimating and Planning (Robert C. Martin Series) - **How much does it cost?** 11136 som with free shipping - **Is it available?** Yes, in stock and ready to ship - **Where can I buy it?** [www.desertcart.kg](https://www.desertcart.kg/products/3700798-agile-estimating-and-planning-robert-c-martin-series) ## 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 Detailed, Proven Techniques for Estimating and Planning Any Agile Project Agile Estimating and Planning is the definitive, practical guide to estimating and planning agile projects. In this book, Agile Alliance cofounder Mike Cohn discusses the philosophy of agile estimating and planning and shows you exactly how to get the job done, with real-world examples and case studies. Concepts are clearly illustrated and readers are guided, step by step, toward how to answer the following questions: What will we build? How big will it be? When must it be done? How much can I really complete by then? You will first learn what makes a good plan-and then what makes it agile. Using the techniques in Agile Estimating and Planning , you can stay agile from start to finish, saving time, conserving resources, and accomplishing more. Highlights include: Why conventional prescriptive planning fails and why agile planning works How to estimate feature size using story points and ideal days--and when to use each How and when to re-estimate How to prioritize features using both financial and nonfinancial approaches How to split large features into smaller, more manageable ones How to plan iterations and predict your team's initial rate of progress How to schedule projects that have unusually high uncertainty or schedule-related risk How to estimate projects that will be worked on by multiple teams Agile Estimating and Planning supports any agile, semiagile, or iterative process, including Scrum, XP, Feature-Driven Development, Crystal, Adaptive Software Development, DSDM, Unified Process, and many more. It will be an indispensable resource for every development manager, team leader, and team member. Review: Buy it NOW! - The book is exceptionally well written. People have said that a book about anything 'Agile' should be thin - well this one is - There are about 24 chapters and each one is no more than easily digestible 20-30 pages for a quick 'agile' read. However, that does make it about 300 pages of content. But here are the 'Great' things about the book: - Well written and a light read with real pearls of wisdom - Well explained concepts with examples - Good primer on Estimation - separating 'duration' from the size and showing how/why it really matters in the long run (of the project) - Explaining when to estimate and a good 'tutorial' on planning poker and Kano Analysis for prioritizing features/desirability. - Throws light on the 'Financial Prioritization' - rubbishing the claim that features in agile teams are prioritized as per the whims and fancies of the developers. - Break downs about planning at multiple levels and what details go in them - Monitoring and communicating plans - the 'how' and 'what' to do I keep referring to the book - because it's really NOT about planning & estimating 'agile projects' - it's about how to be agile with the planning/estimating activity itself. You could use a lot of ideas (especially Kano Analysis, Planning Poker etc.,) and augment it with the approach in your organization (or your own planning exercise) to help communicate the plans/ideas more effectively. Do keep in mind, however - this is NOT a silver bullet that'd end the planning woes encountered in today's software development projects. The case study in the end is too idealistic where everybody is just 'willing' to participate and do it perfectly in lock step synchrony! (It's really difficult to find such software developers in the real world). However, the intent of the case study is to elucidate the concepts covered in the book and hence is a good summary of the ideas presented. There is nothing in the book that says what to do if the client doesn't know what he/she wants? IKIWISI = I'll know it when I'll see it - It doesn't cover anything about prototyping to get the requirements/user stories - it probably assumes that you can get them elicited with ease and moves on from there. In my opinion/experience there is a great deal of concurrency/backtracking with the initial prototyping and eliciting the user stories - an iterative exercise. Once you do those you are probably a bit better off with being able to 'guestimate' the story points. Kano Analysis has known to be around for quite a while and I was aware of it's use in KJ analysis (VOC+ KJ + Kano + Conjoint analysis that is part of the 6-sigma process) - however, it was a refreshing thought to be useful for just about every software product and it could be done without much overhead (actually the overhead is there, however, if the planning is done as a team, it'd be lighter :) Creating the questionnaire for Kano analysis itself takes some time/effort - but is easier once the stories are there. But 'shortening' it to be an 'agile' questionnaire DOES take time/effort. More so based on the feedback you get you may want to update it! But it's worth knowing and probably considering during the planning and user-story elicitation - just before prioritizing! All in all a great read with REAL practical and workable advice/knowledge! Review: Pactical, Easy read. Answers what, why and how. - The book is well structured and easy to read. In my humble opinion, it comes with a strong "buy" rating for any Agile practitioner or a current PMI certified person who wants to contribute to the knowledge economy of ever changing requirements. The book is right sized (finish in a coast to coast trip in US). Practical in its content, it provides lots of examples and case studies, from software as well as non software fields to illustrate the concepts. The detailed case study at the end of the book is invaluable. Several chapters were much thought provoking, specially how to handle team dynamics and cross team estimation. The book did not right fully delve into any details of that, it's a topic for another time. Part I of the books sets up the context. Part II details on estimating the size, and the techniques and tools for doing that; in fact it comes with some simple tools, which can be really customized and expanded quickly. Part III caters to what I call "value add planning" planning the work by prioritizing by business value, The books touches the concepts of financial project analysis, however there are better books for that, and the author provides the references. Part IV brings in the concept of time, and the handling of "estimating for effort" and estimating for duration" is simply superb. Also an entire chapter is dedicated to Buffering and its need and for multi-team projects. Part V presents tools and motivations for monitoring and communicating. Part VI presents why Agile Planning works, and honestly I skipped it, expect the guidelines ( Page 254) which I read to validate my knowledge. If there is one thing that I would change in the book, it would be the story point example with dogs. It would be a little confusing if you have no idea how a Great Dane would be different from a Duchshund! But hey, I think the book gets the message across very well. What I would like to see in the second edition-- softcopy of some tools that goes with the book, may be some templates that can be customized...but then again, you should not be in this business unless you are able to cook these tools up yourself !! ## Features - Physical Book: A tangible copy - Free Delivery - Ebook Option: Purchase from major ebook vendors, like InformIT.com ## Technical Specifications | Specification | Value | |---------------|-------| | Best Sellers Rank | #208,559 in Books ( See Top 100 in Books ) #33 in Software Design & Engineering #173 in Software Development (Books) #577 in Business Technology | | Customer Reviews | 4.6 out of 5 stars 649 Reviews | ## Images ![Agile Estimating and Planning (Robert C. Martin Series) - Image 1](https://m.media-amazon.com/images/I/71yIqYm7obL.jpg) ## Customer Reviews ### ⭐⭐⭐⭐⭐ Buy it NOW! *by P***D on January 21, 2011* The book is exceptionally well written. People have said that a book about anything 'Agile' should be thin - well this one is - There are about 24 chapters and each one is no more than easily digestible 20-30 pages for a quick 'agile' read. However, that does make it about 300 pages of content. But here are the 'Great' things about the book: - Well written and a light read with real pearls of wisdom - Well explained concepts with examples - Good primer on Estimation - separating 'duration' from the size and showing how/why it really matters in the long run (of the project) - Explaining when to estimate and a good 'tutorial' on planning poker and Kano Analysis for prioritizing features/desirability. - Throws light on the 'Financial Prioritization' - rubbishing the claim that features in agile teams are prioritized as per the whims and fancies of the developers. - Break downs about planning at multiple levels and what details go in them - Monitoring and communicating plans - the 'how' and 'what' to do I keep referring to the book - because it's really NOT about planning & estimating 'agile projects' - it's about how to be agile with the planning/estimating activity itself. You could use a lot of ideas (especially Kano Analysis, Planning Poker etc.,) and augment it with the approach in your organization (or your own planning exercise) to help communicate the plans/ideas more effectively. Do keep in mind, however - this is NOT a silver bullet that'd end the planning woes encountered in today's software development projects. The case study in the end is too idealistic where everybody is just 'willing' to participate and do it perfectly in lock step synchrony! (It's really difficult to find such software developers in the real world). However, the intent of the case study is to elucidate the concepts covered in the book and hence is a good summary of the ideas presented. There is nothing in the book that says what to do if the client doesn't know what he/she wants? IKIWISI = I'll know it when I'll see it - It doesn't cover anything about prototyping to get the requirements/user stories - it probably assumes that you can get them elicited with ease and moves on from there. In my opinion/experience there is a great deal of concurrency/backtracking with the initial prototyping and eliciting the user stories - an iterative exercise. Once you do those you are probably a bit better off with being able to 'guestimate' the story points. Kano Analysis has known to be around for quite a while and I was aware of it's use in KJ analysis (VOC+ KJ + Kano + Conjoint analysis that is part of the 6-sigma process) - however, it was a refreshing thought to be useful for just about every software product and it could be done without much overhead (actually the overhead is there, however, if the planning is done as a team, it'd be lighter :) Creating the questionnaire for Kano analysis itself takes some time/effort - but is easier once the stories are there. But 'shortening' it to be an 'agile' questionnaire DOES take time/effort. More so based on the feedback you get you may want to update it! But it's worth knowing and probably considering during the planning and user-story elicitation - just before prioritizing! All in all a great read with REAL practical and workable advice/knowledge! ### ⭐⭐⭐⭐⭐ Pactical, Easy read. Answers what, why and how. *by D***N on November 25, 2005* The book is well structured and easy to read. In my humble opinion, it comes with a strong "buy" rating for any Agile practitioner or a current PMI certified person who wants to contribute to the knowledge economy of ever changing requirements. The book is right sized (finish in a coast to coast trip in US). Practical in its content, it provides lots of examples and case studies, from software as well as non software fields to illustrate the concepts. The detailed case study at the end of the book is invaluable. Several chapters were much thought provoking, specially how to handle team dynamics and cross team estimation. The book did not right fully delve into any details of that, it's a topic for another time. Part I of the books sets up the context. Part II details on estimating the size, and the techniques and tools for doing that; in fact it comes with some simple tools, which can be really customized and expanded quickly. Part III caters to what I call "value add planning" planning the work by prioritizing by business value, The books touches the concepts of financial project analysis, however there are better books for that, and the author provides the references. Part IV brings in the concept of time, and the handling of "estimating for effort" and estimating for duration" is simply superb. Also an entire chapter is dedicated to Buffering and its need and for multi-team projects. Part V presents tools and motivations for monitoring and communicating. Part VI presents why Agile Planning works, and honestly I skipped it, expect the guidelines ( Page 254) which I read to validate my knowledge. If there is one thing that I would change in the book, it would be the story point example with dogs. It would be a little confusing if you have no idea how a Great Dane would be different from a Duchshund! But hey, I think the book gets the message across very well. What I would like to see in the second edition-- softcopy of some tools that goes with the book, may be some templates that can be customized...but then again, you should not be in this business unless you are able to cook these tools up yourself !! ### ⭐⭐⭐⭐ Getting up to speed on agile? Start here. *by K***H on February 22, 2010* After having read many books on agile software development, this is the book that finally made the entire system hang together for me. Cohn walks through all of the various aspects of agile planning, providing reasoning about why various approaches are taken as well as how to go about executing them. While the flow of the book can be a bit jarring at times, jumping from one topic to a seemingly unrelated one between chapters, I still came away from the book with a much better understanding of the end-to-end agile planning process. The book only briefly covers multi-team planning so further reading regarding this may be warranted if you have that need. There are also sections of the book that gloss over some rather large topics (Kano studies, as an example) but the light coverage and accompanied references can lead to jumping off points for those who want more information. A few sections do contain essentially throw-away recommendations (such as the section on task breakdown of stories) but such sections are often in areas that real-world teams will have experience anyhow so it wasn't a big detractor for me. Lastly, if you're looking for advice on running an agile process with a distributed (off-shore) team, this book doesn't touch on any of those challenges. As with most books on agile, this book carries on the tradition of focusing solely on the people processes without any recognition that certain *engineering* processes or practices (test-driven, continuous integration, etc) are necessary for long-term sustainability of an agile process. This is my number one complaint with all agile process books, and I've yet to find one that states, let alone defines, a certain level of software engineering organizational maturity is necessary before embarking on an agile process. Despite these few drawbacks, this book did succeed in finally making the entire agile planning process click for me personally. After reading several of Ken Schwaber's books on the same topic I understood agile in the abstract but this book really brought it all together into a cohesive, pragmatic approach for me. ## Frequently Bought Together - Agile Estimating and Planning - User Stories Applied: For Agile Software Development - Coaching Agile Teams: A Companion for ScrumMasters, Agile Coaches, and Project Managers in Transition (Addison-Wesley Signature Series (Cohn)) --- ## 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.kg/products/3700798-agile-estimating-and-planning-robert-c-martin-series](https://www.desertcart.kg/products/3700798-agile-estimating-and-planning-robert-c-martin-series) --- *Product available on Desertcart Kyrgyzstan* *Store origin: KG* *Last updated: 2026-05-16*