Welcome to the The Art of Agile Development website. Think of this as the "special features" DVD for the book, only without the DVD. (If you haven't bought the book yet, that's okay... we won't tell if you don't.) Here, you'll find a cornucopia of bonus material, such as downloadable posters, behind-the-scenes material, and new insights.

For more bonus material, see the table of contents.

(If there's nothing else on this page, this chapter has yet to be posted. Try the table of contents instead.)

 Print

The Art of Agile Development: Release Planning

24 Sep, 2008

in 99 words

Maximize your return on investment by:

  1. working on one project at a time;
  2. releasing early and often;
  3. adapting your plans;
  4. keeping your options open; and
  5. planning at the last responsible moment.

Use timeboxing to control your schedule. Set the release date, then manage scope to meet that date. This forces important prioritization decisions and makes the endpoint clear.

Prioritized Minimum Marketable Features (MMFs) and stories form the body of your plan. Demonstrate your progress as you develop and use that feedback to revise your plan.

To minimize rework, develop the details of your requirements at the last responsible moment.

Webinar

Maximizing Value with Agile Release Planning

Commentary

A Tale of Two Vacations

Inside the Book

  • Release Planning
  • One Project at a Time
  • Release Early, Release Often
  • Sidebar: Benefits for Programmers
  • How to Release Frequently
  • An Example
  • Sidebar: Customers and Frequent Releases
  • Adapt Your Plans
  • Keep Your Options Open
  • How to Create a Release Plan
  • Sidebar: "Done Done" and Release Planning
  • Planning at the Last Responsible Moment
  • Sidebar: Adaptive Planning in Action
  • Adaptive Planning and Organizational Culture
  • Questions
    • I thought we were supposed to release every week. Is this different?
    • If we don't plan the entire project in detail, what should we tell our stakeholders about our plans?
    • Planning at the last responsible moment means we can't show exactly what we'll deliver. Doesn't that require too much trust from stakeholders?
    • If we use short planning horizons, how can we be sure we'll deliver on the project vision?
  • Results
  • Contraindications
  • Alternatives
  • Further Reading


Loading...

Loading comments...