Expanding and Sustaining Agile in an Organization
What this domain tests
Expanding and Sustaining Agile in an Organization tests scaling beyond a single team. Expect questions on value-stream alignment, dependency management, lean governance and funding, agile contracts, communities of practice, internal coaching, and how to sustain change after a pilot succeeds.
Core rules and concepts
- Scaling extends agile principles across value streams; it is not simply multiplying team ceremonies.
- Organize around customer value and make dependencies visible. Coordinate through shared backlogs, synchronization events, and communities rather than command-and-control reporting.
- Governance and funding must support adaptation: lean funding, evidence-based stage gates, adaptive budgets, and contracts that allow scope change.
- HR, finance, legal, and procurement are part of the system. Agile in delivery cannot compensate for annual budgets and fixed-scope contracts that punish learning.
- Sustainment requires internal coaches, communities of practice, leadership development, meaningful metrics, and organization-level retrospectives.
- Frameworks such as SAFe, LeSS, Nexus, and Scrum@Scale are options, not outcomes. Select and adapt based on context.
- Change should be participative and iterative. Big-bang mandates create compliance without agility.
Worked example
A pilot team succeeds with agile delivery. Leadership then mandates that every team adopt identical ceremonies and tools. Annual funding and fixed-scope contracts remain unchanged, and cross-team dependencies are managed through weekly status reports. Six months later, teams comply with the ceremonies, but value flow has stalled.
Reasoning: the organization scaled team practices without changing system conditions. Dependencies and funding cycles still reward local optimization and plan adherence. The remedy is to map value streams, adapt funding and contracts, create communities of practice, and let teams adjust practices while measuring flow and outcomes.
Traps that cost marks
- Treating a scaling framework as a silver bullet rather than a set of patterns.
- Scaling by mandate and measuring adoption by ceremony count.
- Ignoring finance, HR, legal, and procurement.
- Assuming agile is an IT-only initiative.
- Removing coaching and change support immediately after the pilot.