The Agile Manifesto was published in 2001 and describes four values and twelve principles. Twenty-four years later, most organisations have adopted the processes — Scrum ceremonies, Jira boards, sprint cycles — but not the values. This is why most Agile transformations produce "Scrumfall" rather than genuine agility.
The Four Values: What They Actually Mean
| Manifesto Value | What it means in practice | What it does NOT mean |
|---|---|---|
| Individuals and interactions over processes and tools | Team conversations take priority over ticket updates | Ignore your Jira board entirely |
| Working software over comprehensive documentation | Ship something users can use before writing the manual | Never document anything |
| Customer collaboration over contract negotiation | Involve users in shaping delivery continuously | Ignore contracts or legal obligations |
| Responding to change over following a plan | Welcome backlog changes when new information arrives | Never plan, just react |
Why Process-First Fails
When an organisation mandates Scrum ceremonies without changing how decisions are made, work is funded, or success is measured, the ceremonies become compliance theatre. Teams run sprints but cannot change priorities mid-PI. Stakeholders attend sprint reviews but do not update the backlog. Retrospectives generate action items that are never completed.
What Mindset Change Looks Like
Mindset change is visible in behaviour, not declarations. Specific indicators of genuine Agile mindset:
- A senior stakeholder attends a Sprint Review, hears user feedback, and says "let's reprioritise Q3" — not "we already committed to this roadmap."
- A developer raises an architectural concern in sprint planning and the team delays the sprint goal to resolve it — rather than building on a known weak foundation.
- A Product Owner kills a feature mid-sprint after seeing analytics data showing low user engagement — rather than shipping it because it was in the plan.
- A Scrum Master declines to track individual developer velocity when asked by management — because they understand it would corrupt the team dynamic.
How Scrum Masters Coach the Mindset Shift
Mindset coaching requires working at the level of belief and assumption, not process. Key SM coaching moves:
- Ask "why" questions: "Why do we estimate in hours rather than relative complexity?" surfaces the assumption that estimates are commitments.
- Make experiments visible: "Let's try running without sprint estimates for two sprints and measure throughput." Small, time-boxed experiments lower the emotional cost of change.
- Create safety for failure: If the first failed sprint triggers blame rather than learning, the psychological safety required for genuine Agile is absent. SM work at this level is often the highest-leverage coaching available.
The Mindset Maturity Ladder
- Compliance: Running ceremonies because we were told to. No behaviour change.
- Adoption: Teams understand the ceremonies and run them faithfully. Some improvement in delivery rhythm.
- Adaptation: Teams modify their Scrum approach based on what works for their context. Retrospectives produce real change.
- Mastery: Agile values inform every decision — not just sprint ceremonies. Teams can teach and spread the practice themselves.