Agile Way of Thinking
The Agile Way of Thinking domain tests whether you can explain why Scrum relies on empirical process control rather than a detailed upfront plan, and whether you can apply the Agile Manifesto and its principles to Product Owner decisions. EXIN Agile Scrum questions here often ask you to choose the response that keeps feedback loops short and decisions just-in-time.
Defined versus empirical work
- Defined process control works when work is repeatable and variables are known: define the steps, then follow them.
- Empirical process control suits complex, changing product work: make work visible (transparency), check it frequently (inspection), and change course (adaptation).
- The three pillars depend on each other. Inspection without transparency is guesswork, and adaptation without authority is theatre.
The Agile Manifesto is about preference
- Four 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.
- The right-hand items still have value; the manifesto sets priority, not prohibition.
- The twelve principles include early and continuous delivery, welcoming changing requirements, self-organizing teams, and regular reflection.
Iterative-incremental delivery and timeboxes
- Deliver a usable increment each Sprint, not one phase of a big release.
- Timeboxing fixes Sprint length and exposes estimation error early; scope is the variable, not the date.
- Pull work when capacity allows and limit work in progress; queues hide problems.
- Decide just-in-time at the lowest responsible level, not everything at the start.
Worked example
A sponsor asks the Product Owner for a complete 12-month requirements specification before development starts. The PO proposes two-week Sprints producing a demonstrable increment, with the backlog refined one or two Sprints ahead. Reasoning: the product is complex and requirements will change; a working increment provides transparency, enabling inspection and adaptation. A detailed specification would delay feedback and lock in assumptions. The PO still provides a product vision and a lightweight roadmap, because empirical does not mean unplanned.
Traps that cost marks
- Agile means no documentation: wrong; documentation is produced when it adds value.
- Empirical means no plan: wrong; plans are forecasts that are revised.
- Timeboxing means scope is fixed: usually time and cost are fixed and scope flexes.
- We follow the plan as a reason to reject new learning: this fails the responding-to-change value.
- Agile is a methodology you install: it is a mindset expressed through practices, not a checklist.