Embrace the challenges of uncertainty and change in software development with Mike Cohn‘s Agile Estimating and Planning. This indispensable guide provides practical strategies for Scrum Masters, Agile Coaches, and all team members looking to refine their planning and estimation skills. Regardless of your role—be it Project Manager or Release Manager—this book serves as a valuable resource for enhancing your product delivery efforts.
In this book review, we delve into the shortcomings of traditional project planning and estimation methods. We will examine how agile techniques and tools assist teams and organizations in transforming project and product uncertainties and risks into more concrete and actionable plans. The book offers robust guidelines and steps for estimation—assessing the scope of work to be done—and planning—effectively implementing and delivering products to customers incrementally.
The Purpose of a Good Plan
Cohn begins by addressing the fundamental purpose of a good plan, which is to transition from high risk and uncertainty to a more controlled and predictable environment. Traditional planning methods have several loopholes that derails the team from implementing a good plan that delivers concrete outcomes:
- Multitasking results in context-switching, which causes further delays and extends the completion time.
- Priority Issues occur when features are not developed in order of importance.
- Activity-based Planning focuses on tasks rather than outcomes, leading to inefficiencies.
- Ignoring Uncertainty by doing upfront planning does not reduce risk. It is through iterative processes that risk and uncertainty are managed.
- Estimates Become Commitments that results in locking teams into unrealistic timelines.
Agile Approach to Planning and Sizing
Cohn advocates for an Agile approach to planning and sizing to mitigate these risks by iterating on these two areas:
- Product Focus involves determining the most important features to be developed.
- Project Focus considers team dynamics and the technical skills of developers to efficiently and effectively implement the work.
Why Agile Planning Works
Cohn’s insights on why Agile planning works are compelling. Here are some highlights:
- Frequent Updates to plans ensure adaptability.
- Multiple Levels of Planning provide various perspectives:
- Daily Planning
- Iteration Planning
- Release Planning
- Feature-based Plans focus on delivering tangible outcomes rather than just completing tasks.
- Small Stories keep work manageable and estimable.
- Team-Level Success Tracking promotes collective ownership.
- No Work in Progress (WIP) ensures completed work moves forward, and unfinished work is replanned.
- Size and Duration Estimation differentiate between estimating work size (story points) and duration (iterations) leads to more accurate timelines.
Part I - Estimating Size
When estimating the size of work in agile projects, Cohn presents two main methods to consider:
- Story Points:
- Are a relative measurement that compares the complexity of tasks.
- Encourage teams to focus on the effort required rather than strict timelines.
- Are not influenced by individual skill levels, making it a universal metric.
- Become faster and more consistent as teams develop a shared understanding of point values.
- Are useful for planning sprints and releases with flexibility.
2. Ideal Days:
- Are time-based estimation assuming 100% focus without interruptions.
- Represents the time a task would take under perfect conditions, not accounting for real-world distractions and delays.
- Are best suited for early project stages when teams are getting familiar with story points.
- Provide an intuitive starting point for teams new to agile methodologies.
Part II - Planning for Value
Cohn emphasizes that the best way to reduce the cost of change is to implement features as late as possible. Prioritization is crucial:
- Determine value using Themes, MoSCoW, and Kano models.
- Consider all types of Cost, including new, retained, and incremental revenue.
- Consider New Knowledge gained during the project.
- Apply risk management.
Part III - Scheduling
Schedules are derived from the estimated size of user stories and their durations:
- High-Level Release Planning sets the roadmap and serves as a guidepost.
- Iteration Planning adds precision and clarity for team alignment.
- Velocity-driven vs. Commitment-driven approaches are used to balance workload and expectations.
Part IV - Tracking and Communicating
The author recommends constant monitoring and transparency of the release and iteration plans. They should not gather dust, but rather be actively reviewed, monitored, and adjusted as necessary. Collaborating with teams to track progress ensures the plans remain relevant and on track for success.
- Leverage Visual Boards (Kanban) for iteration and release plans.
- Apply Continuous Monitoring and updating of plans.
- Have honest Communication about progress and challenges.
- Incorporate Metrics and Visual Tools like burndown charts, boards, and end-of-iteration summaries to make work progress transparent and guide future plans.
Mike Cohn’s Agile Estimating and Planning is a well-structured, insightful guide that balances theory with practical application. The book is written from the perspective of traditional projects with defined start and end dates, but its principles are equally applicable to long-term Agile teams. Cohn’s use of real-life examples and clear explanations makes complex concepts accessible and actionable.
In his work, Cohn delves into crucial aspects of estimation and planning, while also warning against practices that can detract from the essence of agile methodologies. Here are some key considerations:
- Teams are advised to shift user story estimation gradually from Ideal Days to Story Points for more precise and enduring planning through relative sizing.
- Encourage a team-oriented approach during iteration planning by steering clear of task allocation and fostering collaboration.
- Embrace collective estimations by the entire team, rather than relying solely on a few individuals.
- Acknowledge uncertainty; upfront planning alone cannot mitigate risks and uncertainties—address them through iterative processes.
- Advocate for story-splitting while preserving the essence of each story, while recognizing that there may be cases when related work may be combined for efficiency.
- Beware of the trap of Parkinson’s Law when engaging in activity-based planning and execution, where tasks tend to expand to fill the allotted time for individuals or teams.
Is agile estimating and planning worth it? Absolutely. By adopting Cohn’s approaches, organizations can make their product delivery more:
- Customer-centric
- Relevant by adjusting to current certainty
- Outcome-driven
- Cost-effective
- Measurable
- Sustainable
Agile Estimating and Planning not only addresses the shortcomings of traditional project management but also provides a roadmap for more effective product delivery. If you’re looking to enhance your Agile practices, this book is a key resource.
Is your organization seeking fresh ideas from proven agile implementation methods? Grab a copy of Mike Cohn’s Agile Estimating and Planning! This book delivers practical strategies for effective planning using iterative techniques in estimation, sizing, scheduling, and progress monitoring. Don’t miss out on unlocking your team’s full potential! 🚀
Want to learn more? Check out our other book reviews on Tribal Unity or Drive.