Agnostic Agile – Know the Basics
This domain, Agnostic Agile – Know the Basics, tests whether you can explain Agile as a principle-driven mindset rather than one branded framework. The exam expects a coach to know the Agile Manifesto and its twelve principles, the logic of empiricism in complex work, and how to choose practices by context. “Agnostic” means framework-neutral and evidence-led, not anti-framework.
Core rules and concepts
- The four values: individuals and interactions over processes and tools; working software over comprehensive documentation; customer collaboration over contract negotiation; responding to change over following a plan. The right-hand items still matter; the left are weighted more heavily.
- The twelve principles include early and continuous delivery of valuable software, welcoming changing requirements, delivering frequently, business and developers working together daily, building projects around motivated individuals, face-to-face conversation, working software as the primary measure of progress, sustainable pace, technical excellence, simplicity, self-organizing teams, and regular reflection and tuning.
- Empiricism requires transparency, inspection, and adaptation. Without transparency, inspection becomes theater and adaptation becomes guesswork.
- Complexity models help decide when predictive and adaptive approaches fit. Cynefin distinguishes clear, complicated, complex, chaotic, and disorder; the Stacey matrix plots agreement and certainty. Complex domains favor safe-to-fail probes and short feedback loops.
- Lean and flow thinking contribute value-stream mapping, waste reduction, small batches, WIP control, and feedback loops.
- Systems thinking means optimizing the whole value stream, not local efficiency in one function.
Worked example
A Scrum team is blamed for missing a fixed-scope date. The coach does not answer “switch to Kanban” or “do more Scrum.” She maps the value stream and finds requirements arrive in large batches, testing is a bottleneck, and the date was set before discovery. She makes the work visible, introduces smaller slices and a daily aging review, and facilitates a trade-off conversation with the product owner and stakeholders. Reasoning: the problem is a system and transparency problem, not a ceremony problem; an agnostic coach selects interventions from Scrum, Kanban, and lean as fit.
Traps that cost marks
- Defining Agile as “Scrum” or “SAFe” only.
- Reciting the four values but not using the twelve principles.
- Treating Cynefin as a labeling exercise rather than a decision aid.
- Reading “agnostic” as “no framework ever” or as “anything goes.”
- Claiming Agile means no documentation or no planning; the manifesto values working software over comprehensive documentation, not instead of it.