InfoQ

News

Planning 101 for Agile Teams

Posted by Deborah Hartmann Preuss on May 25, 2006

Community
Agile
Topics
Leadership ,
Agile in the Enterprise
Tags
Planning ,
Budgets
From the outside, one could see how detractors might assume that "Agile teams don't plan". What do you mean, you don't use MS-Project? Where are the Gantt charts? How do you know if you'll succeed if you don't track actuals against a plan? (Agilists ask: what makes you think you'll succeed just because you are tracking this? :-)

Planning is actually critical and central to Agile work, because of its empirical nature. Agile teams plan, execute, inspect, adapt... plan again.

On the Rally Software corporate blog, coach Stacia Heimgartner has outlined five levels of planning which help set good expectations with all levels of the organization. The level of detail at each level is appropriate to the audience, and accuracy of estimates increases as one moves from the executive "Make it So: at Level 1 to the team's "Making it So" at level 5:
  • Level 1: Vision Planning – Product owner and executives.
  • Level 2: Release Roadmap Planning – Product owner, executives and team.
  • Level 3: Release Planning – Product owner, stakeholders and team.
  • Level 4: Iteration Planning – Team (with product owner).
  • Level 5: Daily Planning – Team (daily status meeting).
For further reading, see Mike Cohn's book, Agile Estimating and Planning.

Related Sponsor

VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.

No comments

Watch Thread Reply

Educational Content

Brian Marick on 4 Challenges and 5 Guiding Values of Agile Software Development

Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).

Are You a Software Architect?

The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?

Agile – A Way of Life and Pragmatic Use of Authority

The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.

Getting Started with Grails, Second Edition

"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?

Using ITIL V3 as a Foundation for SOA Governance

Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.

Adrian Colyer on AspectJ, tc Server and dm Server

SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.

Adam Wiggins on Heroku

Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.

SOA as an Architectural Pattern: Best Practices in Software Architecture

For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.