Living Charter

Definition

A living charter is a visible, prominently posted team charter that is regularly amended as the team and its context evolve. Rather than a document written once and filed away, it serves as a continuously updated reference that the team uses to guide decisions and examine assumptions. The charter becomes a learning instrument, not a record of initial intentions.

In the Book

Larsen and Nies emphasize that the chartering process is about creating ongoing collective understanding, not about completing a document. After creating the first draft during the liftoff event, the team creates a big visible poster that states the product vision, team mission, and mission tests and keeps it posted in the team workspace.

The book provides explicit guidance for amendment: "When the current charter no longer matches what the team needs, change it. The team convenes a meeting to revise the charter whenever anyone (in or out of the team) notices that it's out of date or when it no longer reflects reality." Revisions happen when everyone can be involved and agree on the new terms. Natural opportunities include iteration retrospectives, Kanban reviews, and release retrospectives, though teams can also schedule specially convened rechartering meetings.

The process of amendment applies the same simple rules as the initial chartering: focus on the whole system, work collaboratively, practice Good Enough for Now, begin in possibility, and learn continuously. The charter evolves as new information becomes available about customers, technology, organizational constraints, or team composition.

The book contrasts this approach with typical practice: many teams write a charter at kickoff, then never look at it again. The living charter assumes reality will shift and that the team's understanding will deepen, so the charter should shift too.

Why It Matters

A living charter bridges the gap between planning (which must be done before work) and adaptation (which must happen during work). It acknowledges that initial intentions, no matter how carefully crafted, will be incomplete or wrong in some ways. By treating the charter as open to revision, teams give themselves permission to learn and adjust without abandoning their initial commitment to having shared agreements. This approach also prevents the charter from becoming an obstacle to learning—a source of "we can't do that because the charter says otherwise." Instead, the charter becomes a tool for examining whether the original assumptions still hold.