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: The Planning Game

01 Oct, 2008

in 99 words

Customers have the most information about value: what best serves the organization. Programmers have the most information about cost: what it takes to implement and maintain those features. And remember, every decision to do something is a decision to not do something else.

The planning game brings together customers and programmers so that they may maximize value while minimizing costs. Anybody may create stories. Programmers estimate the stories, and customers prioritize them. Programmers and customers may question each others' decisions, but each group has final say over its area of expertise.

The end result is a single prioritized list.

Commentary

Coulda, Shoulda, Woulda

Inside the Book

  • The Planning Game
  • How to Play
    • Overcoming disagreements
  • Sidebar: On Disappointment
  • How to Win
  • Questions
    • Won't programmers pad their estimates or slack off if they have this much control over the plan?
    • Won't customers neglect important technical issues if they have this much control over the plan?
    • Our product manager doesn't want to prioritize. He says everything is important. What can we do?
  • Results
  • Contraindications
  • Alternatives


Loading...

Loading comments...