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 you're getting a 404, this chapter has yet to be posted. Try the table of contents instead.)

 Print

The Art of Agile Development: Vision

17 Sep, 2008

in 99 words

Every project needs a single vision, and the product manager must unify, communicate, and promote that vision.

Distance between visionaries and the product manager increases error and waste. If you only have one visionary, the best approach is for him to be product manager. Alternatively, use the visionary's protogé.

Some projects have multiple visionaries. They need to combine their ideas into a unified vision. The product manager facilitates discussion and consensus.

Document the vision with what success is, why it's important, and how you know you've achieved it. Post it prominently and involve your visionaries in planning and demos.

Commentary

The Case of the Missing Visionary

Inside the Book

  • Vision
  • Product Vision
  • Where Visions Come From
  • Identifying the Vision
  • Documenting the Vision
  • How to Create a Vision Statement
  • Promoting the Vision
  • Questions
    • Discussing the vision has led to contentious arguments. Should we stop talking about our vision?
    • Our organization already has a template for vision statements. Can we use it?
    • Our visionary finds it very difficult to communicate a cohesive vision. What can we do when it changes?
    • Can individual iterations and releases
    • Isn't it a risk to reduce the amount of documentation?
  • Results
  • Contraindications
  • Alternatives
  • Further Reading

Loading...

Loading comments...