Values Traceability

Definition

Values traceability is the deliberate practice of establishing and maintaining explicit connections from an organization's stated agile values, through the frameworks and ceremonies that embody them, to the specific behaviors team members demonstrate. Without traceability, values become marketing language and ceremonies become hollow rituals. With it, an organization can verify whether teams are genuinely exhibiting agile values or merely performing agile roles.

In the Book

Dalton emphasizes that the Valuing holon (within the Leading performance circle) requires establishing "traceability from agile values to the frameworks, ceremonies, and techniques being adopted within their organization, and verify it through engagement and observation." The book provides concrete steps: after selecting values (transparency, collaboration, learning, failing fast, etc.), leaders must explicitly name which frameworks enable each value (e.g., retrospectives enable learning and continuous improvement; pair programming enables collaboration). Then, during Gemba Walks, leaders observe whether team behaviors actually demonstrate these values. If a team is running daily standups but nobody speaks openly, or doing retrospectives but ignoring feedback, the behaviors don't trace back to the stated values—signaling either that values are not genuinely adopted or that the ceremonies are being performed mechanically without understanding. The Agile Performance Holarchy makes this traceability visible as a design principle rather than an afterthought.

Why It Matters

Values traceability provides a diagnostic tool that prevents the most common failure mode of agile adoption: ceremony without culture. It moves assessment from "are we doing agile?" (ceremonies) to "are we being agile?" (values embodied in behaviors). For large organizations, this becomes the missing layer between abstract values and concrete practices, giving leaders a repeatable method to ensure that agile transformation is actually changing how work gets done, not just renaming roles or adding meetings. It also reveals where the real work of transformation lies: not in adopting new tools, but in closing gaps between stated values and actual behavior.