Agile Chartering¶
Definition¶
Agile chartering is a lightweight, minimum-documentation approach to creating initial understandings, agreements, and alignment about work and how it will be accomplished. It transforms abstract ideas into manageable work efforts by balancing the interests and capabilities of all parties, and it creates a living reference document that guides and supports the work while remaining open to renegotiation when conditions change.
In the Book¶
Larsen and Nies present chartering as a two-stage process: first, sponsors and product managers develop a rough-draft purpose statement offline; second, the whole team and key stakeholders come together to refine, challenge, and own that draft. The chartering event itself is less important than the conversations that develop it. One colleague quoted in the book says: "Chartering is a discovery and negotiating activity...The charter serves as a contract that guides and supports the work. It provides a reference point for renegotiations when conditions change."
The System Tracking Project case study illustrates this principle: when support representatives remained silent during a chartering meeting, the product manager specifically asked for their perspective. A developer's suggestion to address one concern led the whole group into a productive discussion that resulted in a mission test everyone agreed to. Later, over lunch, the product manager remarked: "It's the chartering process that's important, more than the charter itself."
Chartering focuses on high-bandwidth, face-to-face communication. The process explicitly uses five simple rules: focus on the whole system, work collaboratively, practice Good Enough for Now (GEFN), begin each endeavor in possibility, and learn continuously as work unfolds. The physical environment matters—natural light, tall ceilings, snacks, and beverages—because people collaborate more effectively in certain conditions.
Why It Matters¶
Agile chartering creates collective understanding by pulling expertise from many perspectives. Rather than a top-down mandate or a bottom-up free-for-all, it creates a shared container where the team shapes both itself and the work. This collaborative approach produces both better decisions (because objections and insights surface) and deeper commitment (because people have had a voice). The charter becomes a living document that the team updates when reality changes, rather than a dusty artifact filed away on day one.