Skip to main content
Enterprise Agile Planning Image

This post is from the CollabNet VersionOne blog and has not been updated since the original publish date.

Last Updated Nov 03, 2009 — Enterprise Agile Planning expert

Five Myths of Agile Development: Myth #2 / Agile Teams Do Not Plan

Enterprise Agile Planning
The first post in this series discussed Myth #1 / Agile is Undisciplined. Now let's talk about another common Agile myth: Agile Teams Do Not Plan. This misconception generally relates to a lack of understanding of an agile, or incremental, planning approach. Most agile teams spend as much, if not more, time planning their projects. The difference is that this planning effort is spread throughout an entire project as opposed to being compressed into the beginning of a project. Intead of extensive, up/front planning, agile development simply follows an incremental approach to planning, which allows for initial planning at a high level and then iteratively planning at lower levels as more knowledge is gained. If we look at the actual results of many traditional project plans, detailed, task/based project plans created at the beginning of a software project often quickly fall out of sync with the technical and business realities of a project. Over time, significant energy is expended in reconciling the original plans to these current realities. On the other hand, agile development accepts this volatility and instead replaces detailed, up/front planning with "continuous planning" // for example, quarterly at the release level, monthly or weekly at the iteration level, and daily at the task and team/member level. Given that the technology, requirements, business demands, people, issues, risks, etc. are almost always in flux in virtually all software projects, this type of continuous planning approach provides the team with the necessary process/based ammunition to much more easily and efficiently adapt to the changes. In addition, teams are also able to incrementally optimize their plans as new information emerges. What is just as important is that as teams begin to learn what they can deliver on a daily, weekly, and monthly basis, they become more accurate at longer/range planning. Many of the agile teams I've worked with have become much more confident in both their short/ and long/term planning abilities than they ever were with traditional planning approaches. Next up: Myth #3 / Agile Development is Not Predictable//////////////////////////////////////////////////////////////////////////////// Read the other posts in this series:Myth #1 / Agile is UndisciplinedMyth #3 / Agile is Not PredictableMyth #4 / Agile Does Not ScaleMyth #5 / Agile is Just Another FadIf you'd like to download this blog series in document (PDF) format, get the Five Myths of Agile Development white paper.

More from the Blog

View more
May 03, 2021

Bringing the agile planning approach to your whole business

Enterprise Agile Planning
The events of the last 12 months have demonstrated that the only sure ...
Read More
Apr 08, 2021

Making IT services more agile

Enterprise Agile Planning
The agile revolution completely transformed how we create digital prod ...
Read More
Feb 14, 2021

Reflecting on the 20th anniversary of the Agile Manifesto

Enterprise Agile Planning
Over the past 20 years, it’s been amazing to watch an idea from ...
Read More
Feb 08, 2021

How does agile apply to an entire organization?

Enterprise Agile Planning
Before we dive into the main subject of this blog post, it is importan ...
Read More
Contact Us