Agile Principles and Mindset
Values before practices
The four Agile Manifesto value pairs - individuals and interactions over processes and tools; working software over comprehensive documentation; customer collaboration over contract negotiation; responding to change over following a plan - rank the left items higher, they do not declare the right items forbidden. Any answer that forbids documentation, contracts, or planning entirely is a trap. The twelve principles convert values into behaviour: early and continuous delivery of value, welcoming changing requirements, frequent working software, business and technical people collaborating daily, building around motivated individuals, face-to-face conversation, working software as the primary measure of progress, sustainable pace, technical excellence, simplicity, self-organizing teams, and periodic reflection and tuning.
Empiricism and complexity
Agile planning rests on empiricism: transparency, inspection, adaptation. The Stacey and Cynefin models explain the why - when requirements and technology are both uncertain, predictive planning fails, so the team inspects and adapts in short cycles. Candidates must separate doing Agile (ceremonies adopted, mindset unchanged) from being Agile (servant leadership, self-organization, trust). Shu-Ha-Ri describes the learning path: follow the rules, adapt them, then transcend them.
Traps
- Picking a process answer when the real gap is feedback, transparency, or trust.
- Assuming the Agile leader assigns tasks, approves estimates, or settles every team dispute.
- Reading the values as absolutes rather than preferences.
Rule of thumb: when two options look sound, choose the one that shortens the feedback loop, raises transparency, and leaves the decision with the people doing the work.