AoAD2 Practice: Task Planning

This is an excerpt from The Art of Agile Development, Second Edition. Visit the Second Edition home page for additional excerpts and more!

This excerpt is copyright 2007, 2021 by James Shore and Shane Warden. Although you are welcome to share this link, do not distribute or republish the content without James Shore’s express written permission.

Task Planning

Audience
Whole Team

We have a plan for this week’s work.

If you follow the practices described in the “Planning” chapter, you’ll end up with a visual plan with multiple levels of detail: valuable increments that could possibly be done in the long-term, small valuable increments that are likely to be done in the medium-term, and specific stories that will be done in the near-term.

That plan turns into action through task planning: breaking down stories into tasks and tracking the team’s progress. Because Agile teams are self-organizing (see the “Key Idea: Self-Organizing Teams” sidebar), task creation, assignment, and tracking is done entirely by the team, not by managers.

There are three parts to task planning: cadence, creating tasks, and visual tracking.

...to continue reading, buy the book!

In this Section

  1. Task Planning
    1. Cadence
      1. Iterations
      2. Continuous flow
        1. Key Idea: Collective Ownership
    2. Creating Tasks
    3. Visual Tracking
      1. Task grid
      2. Detectives’ whiteboard
    4. Cross-Team Dependencies
    5. Making and Meeting Iteration Commitments
    6. Incomplete Stories
    7. Emergency Requests
    8. Your First Week
    9. Questions
    10. Prerequisites
    11. Indicators
    12. Alternatives and Experiments
    13. Further Reading

Discuss the book on the AoAD2 mailing list or Discord server. Or come to the weekly book club!

For more excerpts from the book, see the Second Edition home page.

If you liked this entry, check out my best writing and presentations, and consider subscribing to updates by email or RSS.