Practices, Methodology, and Mindset

Definition

The book distinguishes three tiers of "going agile." At the bottom, individual practices (a daily standup, a task board) can be adopted by anyone, but each person interprets and uses them through their own role, which is what produces a fractured perspective and better-than-not-doing-it results. Above that, a methodology — Scrum or XP — is "a collection of practices combined with ideas, advice, and a community of practitioners": adopting it whole forces the team to reconcile how the practices interact and think together about why they're doing them. Above even that sits mindset: the book states plainly that "Lean is not a methodology. Rather, it's a name for a mindset — it has its own set of values, and thinking tools to help you adopt it." A mindset is what a methodology is supposed to instill in its practitioners once the practices and their shared understanding have taken root.

In the Book

Chapter 2 makes the case by comparing Scrum, XP, Lean, and Kanban directly (pages 43-44): Scrum and XP are both iterative methodologies with different focuses — Scrum on project management and self-organization, XP on collaboration, planning, and holistic design practices — while Lean is explicitly not a methodology but a mindset with its own values and thinking tools, and Kanban is "an agile method... built on the values of Lean." The book argues that a daily standup can be run two totally different ways depending on whether the team has absorbed the underlying values: run well, it's a collaborative check-in; run poorly, it degenerates into a status meeting where "each developer... tell[s] the project manager, 'Here are obstacles blocking my way — you go deal with them,'" a team that "may have adopted Scrum-like practices, but they aren't using Scrum." What ties Scrum, XP, and Lean together despite entirely different practices and focuses is that "all agile methodologies are based on the same principles" — the Agile Manifesto's values sit underneath all of them, which is what makes adopting the whole methodology (not just its individual practices) "the opposite of a fractured perspective."

Why It Matters

This gives a vocabulary for a common confusion: two teams can claim to be doing "the same thing" — Scrum, a diet, a management framework — while producing wildly different results, because one has adopted the surface practices and the other has genuinely internalized the values underneath them. It reframes "we tried X and it didn't work" as a question of which level was actually adopted, and it explains why some frameworks (Lean) resist being reduced to a checklist at all — they were never meant to be practices in the first place, only a mindset expressed through whichever practices a team builds to embody it.