InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Planning 101 for Agile Teams

Posted by Deborah Hartmann Preuss on May 25, 2006

Sections
Process & Practices
Topics
Leadership ,
Agile in the Enterprise ,
Agile
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.
  • This article is part of a featured topic series on Agile

No comments

Watch Thread Reply

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.