Agile software development is built on adaptability, collaboration and continuous delivery of value, yet one of its biggest challenges lies in estimating and planning effectively in such an environment. Mike Cohn’s Agile Estimating and Planning provides one of the most comprehensive and practical guides to tackling this challenge. The book moves beyond rigid traditional planning approaches and offers techniques that allow teams to estimate accurately enough to make commitments, while retaining flexibility to respond to change. It focuses on helping teams create reliable plans that drive progress rather than constrain it, with an emphasis on delivering value rather than sticking to arbitrary deadlines.
The Purpose of Agile Planning
Cohn begins by addressing a fundamental misunderstanding: planning is not about predicting the future with certainty. Instead, it is about reducing uncertainty and setting expectations responsibly. Agile planning provides a framework for making informed decisions, adjusting to feedback and guiding the team towards delivering the most value within available constraints. Plans are meant to evolve as more is learned about the work, the technology and the customer’s needs.
Traditional planning often aims for precision far beyond what is possible at the start of a project. Agile approaches recognise that the future is unpredictable, so plans should be living documents that evolve with experience. Cohn positions agile planning as an exercise in risk management rather than control. Teams create plans that are realistic and flexible, allowing them to deliver incremental value and adjust course when necessary.
The Hierarchy of Planning
Cohn describes planning as happening at multiple levels, each serving a different purpose. At the highest level is the vision, which outlines the overall goal or product strategy. Below this is the roadmap, which lays out the major releases or milestones. Release planning then defines what can realistically be delivered within a release timeframe, while iteration planning focuses on the details of what the team will deliver in the next short cycle, typically one to four weeks. Finally, the daily plan helps keep the team aligned through brief daily stand-ups and visible task boards.
Each level of planning feeds into the next. The product vision provides the context for release planning, which in turn informs iteration plans. Cohn stresses that agile teams plan just enough at each level to make good decisions, avoiding unnecessary detail that will likely change. The goal is to ensure that every plan remains useful and relevant, not to create documentation for its own sake.
Estimation: The Heart of Planning
Effective planning depends on good estimates, and Cohn spends much of the book helping readers understand how to estimate well in an agile context. He distinguishes between estimation and commitment. Estimation is about understanding effort, uncertainty and complexity, while commitment is about deciding what to deliver by a certain time. Confusing the two leads to pressure, poor quality and missed deadlines.
Agile teams estimate work in relative rather than absolute terms, using techniques like story points or ideal days. Story points measure the relative size or complexity of user stories compared to one another. This allows teams to focus on comparative reasoning rather than trying to guess exact durations. For example, if one story feels twice as difficult as another, it can be assigned twice as many points. Over time, as teams complete work and measure their velocity (the average number of points completed per iteration), they can make increasingly reliable forecasts.
Cohn encourages teams to avoid false precision and instead embrace ranges and probabilities. He also reminds readers that estimates are best made collaboratively. By involving the entire team, diverse perspectives are considered, and shared ownership of the plan increases. Techniques such as Planning Poker bring structure and consensus to the estimation process while keeping it engaging.
Velocity and Predictability
Velocity plays a key role in agile planning. It represents the team’s capacity to deliver value per iteration, measured in story points or another relative metric. While initial velocity may be uncertain, it stabilises after a few iterations, allowing teams to make evidence-based projections. Cohn advises against overanalysing velocity or using it as a performance metric. It should be a tool for forecasting, not a weapon for management pressure.
The book explains that variability in velocity is normal and healthy. Some iterations will deliver more, others less. Instead of demanding unrealistic consistency, agile teams should plan around expected ranges, acknowledging uncertainty. Over time, a reliable pattern emerges that supports confident release planning.
Prioritisation and Value Delivery
In traditional projects, work is often scheduled in arbitrary order, leading to late discovery of critical issues and delayed value. Cohn’s approach puts business value at the centre of planning. He offers several practical methods for prioritisation, including the use of themes, risk reduction, and cost of delay.
The Product Owner plays a crucial role in prioritising the backlog to maximise return on investment. The team should focus first on delivering the highest-value and highest-risk items. Early delivery of valuable features provides feedback, reduces uncertainty and helps stakeholders make better decisions. Agile planning is therefore iterative not only in execution but also in the discovery of what truly matters to the customer.
Cohn also introduces the concept of the “iron triangle” of scope, schedule and cost. Traditional approaches fix scope and adjust time and cost to meet it. Agile reverses this thinking by fixing time and cost, then flexing scope to maximise delivered value. This approach enables teams to deliver the best possible outcome within real-world constraints.
Release Planning
Release planning bridges the gap between high-level product goals and short-term iterations. Cohn offers a structured approach that begins with establishing the vision and success criteria for the release. The team then estimates and prioritises backlog items, determines their expected velocity and projects how many iterations are needed to complete the desired scope.
However, Cohn cautions that release plans should never be static. They should be revisited frequently as new information emerges. If a team’s velocity changes, or if customer feedback alters priorities, the release plan must adapt. By reviewing progress at the end of each iteration, teams maintain transparency and control without falling into the trap of rigid prediction.
Cohn also explains how to communicate uncertainty to stakeholders. Instead of promising a single fixed date, agile teams can use probabilistic forecasting to express likely delivery ranges. This honesty builds trust and reduces disappointment, while still providing enough predictability for business decisions.
Iteration Planning
Iteration planning is where long-term goals meet short-term execution. The team selects user stories from the prioritised backlog and commits to completing them in the next iteration. Cohn emphasises that commitment must be realistic and owned by the team, not imposed externally.
The team breaks each story into smaller tasks, estimates effort and checks that total workload aligns with available capacity. Planning should be lightweight and collaborative, often taking no more than a few hours. By the end of the session, everyone should have a shared understanding of what will be delivered and how it will be achieved.
Cohn’s advice is practical: plan enough to remove ambiguity but avoid over-planning that restricts flexibility. He also highlights the importance of including testing and integration work within the iteration plan, ensuring that what is delivered is truly done.
Tracking Progress
Tracking in agile projects relies on transparency and simplicity rather than heavy documentation. Cohn introduces tools such as burndown charts and task boards to visualise progress. These help teams see whether they are on track, identify emerging problems early and adjust plans accordingly.
Burndown charts show how much work remains over time, providing a clear picture of progress towards the goal. Velocity trends can also indicate whether the team’s estimates are accurate or if systemic issues are affecting delivery. Cohn encourages teams to use such data for learning, not blame. The aim is continuous improvement, not punishment.
He also advocates measuring value delivered, not just tasks completed. This mindset ensures that teams focus on outcomes rather than output. Stakeholders care about business results, not how many lines of code were written. Agile planning must therefore connect every piece of work to its intended impact.
Dealing with Uncertainty
Every plan is wrong to some degree, and Cohn makes this point repeatedly. The key is to make it “wrong in the right direction” by planning for learning. Agile estimation and planning embrace uncertainty through iteration, feedback and incremental delivery.
Cohn presents techniques for managing uncertainty, such as using ranges instead of single-point estimates, regularly revisiting plans and adjusting based on actual results. By inspecting and adapting frequently, teams keep their plans accurate enough for decision-making without wasting effort on false precision.
Risk management is also central to Cohn’s approach. By delivering high-risk and high-value items early, teams learn faster and reduce exposure. The iterative nature of agile ensures that lessons from one cycle feed into the next, creating a continuous loop of improvement.
Scaling and Organisational Challenges
While much of Cohn’s guidance applies to small teams, he also addresses scaling agile planning across larger organisations. He acknowledges that coordination becomes more complex as multiple teams work on shared goals, but the same principles apply: transparency, regular feedback and adaptive planning.
He suggests techniques such as shared release planning sessions, synchronised iterations and centralised product backlogs. The challenge lies not in scaling the mechanics of planning but in maintaining agile values at scale. Teams must remain empowered, and decision-making must stay close to where the work happens.
Cohn warns against reverting to command-and-control models as organisations grow. Agile planning thrives on collaboration and trust, and these must be preserved even when managing dozens of teams.
Estimating Non-Software Work
One of the strengths of Cohn’s approach is its broad applicability. He demonstrates that agile estimating and planning are not limited to software development. Any type of project that benefits from iterative delivery and adaptive learning can use these principles.
He provides examples from infrastructure, marketing and research projects, showing how story-based estimation and timeboxed planning can apply in diverse contexts. The key is focusing on delivering increments of value and using empirical data to guide future plans.
Common Pitfalls and How to Avoid Them
Cohn concludes by addressing common mistakes teams make when adopting agile estimation and planning. One is treating estimates as commitments, which leads to unrealistic promises and erodes trust. Another is failing to re-estimate as the project evolves, which leaves plans outdated and misleading.
He also warns against focusing solely on velocity as a success measure. A team that completes many points but delivers little value is not succeeding. Similarly, overemphasis on tools can distract from the underlying goal: fostering collaboration and shared understanding.
Cohn’s recurring advice is to view planning as an ongoing dialogue. Good planning is about communication, alignment and decision-making, not producing perfect documents. Agile estimation and planning are successful when they help teams make better choices and deliver meaningful outcomes.
Why This Book Matters
Agile Estimating and Planning remains one of the most practical and enduring guides for anyone working in agile environments. Cohn bridges the gap between theory and execution, offering techniques that work in real-world teams. His advice helps organisations strike a balance between adaptability and predictability, ensuring that planning serves delivery rather than hindering it.
The book’s greatest value lies in its realism. Cohn does not promise certainty or perfect forecasts; instead, he shows how to make uncertainty manageable. Teams that adopt his principles find that planning becomes less about control and more about confidence. They deliver more value, adapt faster and build stronger trust with stakeholders.
Ultimately, Cohn’s message is simple: planning is not a one-time event, but a continuous, collaborative process that evolves with learning. Agile teams succeed when they plan to learn, and learn to plan.
Do You Want To Learn Scrum & Agile?
Learn Scrum & Agile at lost cost and online. Our 5-star rated Ultimate Scrum & Agile eLearning Courses can take you from beginner to advanced at your own pace.
Prepare and practice for the assessments from the major Scrum & Agile providers. Our 5-star rated Ultimate Scrum & Agile Practice Assessments will help you gain certification.
About TheScrumMaster.co.uk
