Synthesized answer
The provided passages state that "Agile Estimating and Planning" guides readers on "what makes a good plan—and then what makes it agile" [2]. The book discusses the "philosophy of agile estimating and planning" and demonstrates "how to stay agile from start to finish" [2].
While the passages indicate that the book addresses "how to schedule projects that have unusually high uncertainty or schedule-related risk" [1], they do not explicitly detail the fundamental characteristic or philosophical approach, beyond specific tools, that makes a plan truly agile in such circumstances. The passages mention learning "what makes a good plan—and then what makes it agile" [2], but the specific philosophical underpinnings for high uncertainty or schedule-related risk are not elaborated upon.
Synthesized from the book passages below. Chat with the book on Feynman for follow-up.
From the book
nancial 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,…
Title: Agile Estimating and Planning by Mike Cohn 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…
More questions about this book
- 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 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?