What is Agile Anyway?
The Agile Manifesto provides four guiding principles:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
According to the practitioners featured in this article, Agile fundamentally means "collaboration and cultivating culture within an organization." Derek Huether describes it as "the embodiment of empowerment and responding to change." Don Gray emphasizes that "Agile is a high order of abstraction" grounded in the Manifesto's principles. Mike Cottmeyer notes that Agile represents "a set of principles expressed through a family of methodologies."
The bottom line: Agile is a set of principles emphasizing flexibility, collaboration, and openness to new approaches rather than rigid adherence to predetermined processes.
Adoption vs. Transformation
There's a crucial distinction between these terms. Adoption refers to implementing Agile principles and practices, while transformation involves the deeper cultural and organizational changes required for genuine success. Don Gray states that "adoption of Agile is taking on principles" whereas "transformation is a more embedded process."
The featured coaches emphasize that organizations can benefit from adopting certain Agile practices, but true transformation requires willingness to fundamentally change how the organization operates.
Individual Readiness Matters
Change begins with individuals. Servant leadership and genuine commitment are essential. Chris Goldsbury warns against dogmatic approaches: "If you are dogmatic about your approach then it will not work." Instead, leaders should lead by example and empower others rather than centralizing decision-making.
Derek Huether advocates for "small wins over time," recognizing that full adoption may not be realistic in every organizational context.
Key Questions Before Implementation
Organizations should honestly address:
- Why do we truly want to change?
- What does success look like?
- What problems are we solving?
- Is our culture ready for increased collaboration and flexibility?
- Does management genuinely support change?
- Are organizational structure and culture aligned?
When Agile Works Best
Mike Cottmeyer identifies ideal conditions: "Agile is a good fit when you're delivering tangible products or dealing with problem domains where you don't know the direction upfront." Conversely, rigid hierarchies and heavily matrixed structures may resist Agile implementation.
Communicating Value to Management
Effective communication requires understanding your audience. Present three key elements:
- Data – Measurable potential improvements
- Small wins – Demonstrable value within controllable areas
- Business focus – Emphasize business value and predictability rather than cultural improvements
Mike Cottmeyer advises: "Very rare that management cares whether you're using Agile or not" – focus instead on delivering desired business outcomes.
Final Takeaway
Agile can work for any organization, but success depends on environmental readiness, genuine commitment to change, and honest assessment of current conditions. Implementation requires patience and incremental steps rather than dramatic transformations. The broader Agile community stands ready to support organizations navigating this journey.