Agile Principles Require Interpretation, Not Mechanical Implementation

Definition

Agile methodologies, by design, are not prescriptive—they do not tell you exactly what to do in every situation. Instead, they define a set of values and principles that require interpretation and intelligent application in a given business context. The Agile Manifesto's four values (individuals and interactions, working software, customer collaboration, responding to change) are relative statements about priorities, not absolute rules. This non-prescriptive nature has led to widespread misinterpretation: some interpret "working software over comprehensive documentation" to mean no documentation at all; others interpret "responding to change" to mean change control is incompatible with agile. Understanding that agile principles require judgment and contextual application—not mechanical execution—is critical for successful implementation.

In the Book

Cobb identifies the root cause of many agile misconceptions: "Agile methodologies, by design, are not prescriptive—they don't tell you exactly what needs to be done to implement the methodology or how to do it in many cases. In general, agile methodologies define some principles that intentionally require interpretation for a given situation."

He cites the Agile Manifesto's four values and notes that some have taken an "extreme view" to interpret them as absolutes: no documentation, no processes and tools, incompatibility with customer contracts, incompatibility with change control. "It certainly wasn't the intent of the people writing the Agile Manifesto that the contents would be interpreted as absolutes—they were intended to be relative statements." He emphasizes: "The key point is that you have to interpret those principles in the context of your business and project environment and apply them intelligently. Unfortunately, that has not always been the case and agile methodologies have been misapplied or poorly implemented in some situations."

He further notes that "implementing agile methodologies [mechanically] 'by the book' is not the right approach. You really need to understand the principles underneath it at a deeper level to know how to apply it in the context of your business and project environment."

Why It Matters

This concept elevates agile understanding from rule-following to principle-based judgment. It explains why cookbook implementations of agile often fail—they treat principles as absolute rules rather than guides that must be adapted. It also explains why different organizations can successfully implement agile in quite different ways: they understand the same underlying principles but apply them differently based on context. The concept transfers to any principle-based approach: to use principles effectively, you must understand their purpose deeply enough to adapt them intelligently, which requires more skill than simply following a procedure. This is what separates expert practice from novice compliance.