InfoQ

News

Planning 101 for Agile Teams

Posted by Deborah Hartmann on May 25, 2006 07:34 AM

Community
Agile
Topics
Agile in the Enterprise ,
Leadership
Tags
Budgets ,
Planning
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

Bindings, Platforms, and Innovation

This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.

Orchestrating Long Running Activities with JBoss / JBPM

This article explores the use of JBoss and jBPM to implement design solutions that effectively address the issue of orchestrating long running activities.

Neo4j - The Benefits of Graph Databases

This presentation covers the use of graph databases as an optimal solution for data that is difficult to fit in static tables, rapidly evolving data or data that has a lot of optional attributes.

Realistic about Risk: Software development with Real Options

This session introduces Real Options and shows how it can help in running your project. Real Options is a decision-making process that can be used to manage risk.

Communication Flexibility Using Bindings

This article discusses the use of bindings on services and references (including the instance of non-configured bindings) as the means to implement SCA communications in a Web and SOA environment.

Writing DSLs in Groovy

After a short introduction to DSLs, Scott Davis plays with the keyboard showing how to approach the creation of a DSL by typing working snippets of Groovy code that get executed.

Scaling Agile with C/ALM (Collaborative Application Lifecycle Management)

IBM Rational and InfoQ present, Scaling Agile with C/ALM, an eBook showing organizations how to become “finely tuned software delivery machines” by enabling team integration and scaling.

Concurrent Programming with Microsoft F#

Amanda Laucher presents a real life enterprise application written in F#. She shows actual code snippets, explaining design decisions and suggesting how to use some of the F# constructs.