EXIN Agile Business Professional: The Agile Mindset

What this domain tests

The Agile Mindset domain examines whether you can distinguish agile as a value system and set of decision habits from agile as a collection of ceremonies. Questions probe the Agile Manifesto values and principles, empirical control under uncertainty, customer-centricity, and the difference between doing agile and being agile.

Core rules and concepts

• The Manifesto's four values are pairwise: 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 retain value; the left are weighted more heavily.
• Agile principles include satisfying the customer through early and continuous delivery, welcoming changing requirements, delivering frequently, business people and developers working together daily, building projects around motivated individuals, face-to-face communication, working software as the primary measure, sustainable pace, technical excellence, simplicity, self-organizing teams, and regular reflection.
• Empirical process control rests on transparency, inspection, and adaptation. It suits complex work where requirements and causes are not fully knowable in advance.
• A mindset is visible in trade-offs: what leaders reward, what teams do when a plan meets new evidence, and whether customers are collaborators or spectators.

Worked example

A team runs daily stand-ups, sprint planning, and retrospectives, yet its annual scope is fixed by finance, change requests are discouraged, and the product owner is measured on delivering every documented requirement. A candidate is asked whether the team is agile.

Reasoning: the ceremonies are present, but the decision system contradicts the Manifesto's preference for responding to change and customer collaboration. This is doing agile rather than being agile. The remedy is not another ceremony; it is to make empirical adaptation legitimate by allowing scope trade-offs, bringing the customer into prioritization, and measuring outcomes.

Traps that cost marks

• Treating agile as no documentation or no planning. The Manifesto values documentation and plans; it rebalances emphasis.
• Confusing speed with agility. Agility is the capacity to change direction economically, not merely to deliver faster.
• Assuming self-organization means no leadership. Agile leadership sets purpose, constraints, and boundaries.
• Selecting follow the plan as the default when new information arrives.