Summary
Agile Estimating and Planning argues that conventional, prescriptive planning fails, and agile planning works by providing practical techniques for estimating and planning agile projects. The book guides readers to answer fundamental project questions like "What will we build?", "How big will it be?", "When must it be done?", and "How much can I really complete by then?". It focuses on how to stay agile from start to finish, saving time and conserving resources by delivering more value more often.
The book details how to estimate feature size using story points and ideal days, explaining when to use each. It covers how to re-estimate, prioritize features with financial and nonfinancial approaches, and split large features into smaller, manageable ones. Techniques are presented for planning iterations, predicting initial progress rates, and scheduling projects with high uncertainty or risk, supporting various agile methodologies.
Key concepts
- Story Points — A method for estimating feature size in agile projects.
- Ideal Days — Another method for estimating feature size, distinct from story points.
- Iteration Planning — The process of planning work within specific timeboxed cycles.
- Feature Splitting — Techniques for breaking down large features into smaller, more manageable units.
- Financial and Nonfinancial Prioritization — Approaches to ordering features based on both economic value and other factors.
From the book
Description: 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…
Snippet: The examples in the book are concrete, easily grasped, and simply reek of common sense. This book will help teams (whether Agile or not) deliver more value, more often, and have fun doing it!
Popular questions readers ask
- The text states that "conventional prescriptive planning fails and why agile planning works." Explain, as if to someone unfamiliar with software development, the core reasons why agile planning is described as more effective in dealing with project uncertainties compared to conventional methods.
- Imagine you are teaching a new team member how to estimate feature size. How would you articulate the fundamental differences between "story points" and "ideal days," and under what specific circumstances would you recommend using one method over the other?
- Cohn discusses "how and when to re-estimate" and "how to prioritize features." How are these two concepts inextricably linked in practice, and what potential negative consequences could arise if a team prioritizes features without adequately re-estimating their effort or size?
- The book guides readers on "what makes a good plan—and then what makes it agile." What fundamental characteristic or philosophical approach, beyond simply using specific tools, is essential for a plan to truly be considered "agile" when facing high uncertainty or schedule-related risk?
- The snippet claims the book helps teams "deliver more value, more often, and have fun doing it!" How do techniques like "splitting large features into smaller, more manageable ones" and "planning iterations" collectively contribute to *both* delivering value more frequently *and* fostering a more enjoyable team experience?