AoAD2 Chapter: Accountability (introduction)

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.

Accountability

If Agile teams own their work and their plans, how do their organizations know they’re doing the right thing? How do they know that the team is doing its best possible work, given the resources, information, and people it has?

Organizations may be willing, even eager, for teams to follow an Agile approach, but this doesn’t mean Agile teams have carte blanche authority to do whatever they want. They’re still accountable to the organization. They need to demonstrate that they’re spending the organization’s time and money appropriately.

This chapter has the practices you need to be accountable:

  • The “Stakeholder Trust” practice allows your team to work effectively with stakeholders.

  • The “Stakeholder Demos” practice provides feedback about your team’s progress.

  • The “Forecasting” practice predicts when software will be released.

  • The “Roadmaps” practice shares your team’s progress and plans.

  • The “Management” practice helps teams excel.

...to continue reading, buy the book!

In this Section

  1. Accountability
    1. Sidebar: Accountability Sources

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.