How the practice works
A charter names the result, scope, dependencies, decision rights and completion condition for a workstream. It is short enough to revisit when new requests arrive. The document becomes useful when it explains why a plausible task belongs somewhere else.
- 01Result
- 02Scope
- 03Dependencies
- 04Completion
A working example
A communications workstream is asked to redesign the service operating model because both affect the launch. The charter identifies the interface: Communications explains the agreed model; the operating owner decides it. The task is routed without losing the dependency.
