Agile transformations often struggle not because teams fail to improve, but because organizations never clearly define what success looks like or how progress should be understood. This session shares a two‑year Agile transformation where meaningful progress emerged only after the organization aligned on a shared definition of Agile maturity and the future state it wanted to achieve.

Success did not depend on a single role or group driving change. Instead, progress came from close collaboration across delivery teams, product and delivery roles, and leadership. Clarifying responsibilities, decision boundaries, and ways of working improved decision making, strengthened backlog practices, and created stronger alignment between business intent and delivery execution.

Visual collaboration tools such as Mural were used to bring cross‑functional groups together to co‑create role definitions, shared ways of working, and a pragmatic Agile maturity model tailored to the organization’s context. The maturity model was intentionally designed as a shared reference point rather than a scorecard, making expectations explicit and helping teams understand what advancing in maturity meant in day‑to‑day behaviors and outcomes.

The session also explores how maturity insights and qualitative observations were synthesized and shared during quarterly business reviews. Rather than focusing on Agile terminology or mechanics, progress was communicated to the CIO through themes of organizational health, alignment, and business outcomes, enabling more meaningful conversations about direction and investment.

Attendees will gain practical insights into how individuals across roles can contribute to large‑scale change by enabling clarity, supporting shared understanding, and helping organizations define success before attempting to measure it.