Opening the book…
Choosing the Right Agile Approach
The right Agile approach depends on context. A team should not choose Scrum just because it's popular, choose Kanban just because it wants fewer meetings, or choose SAFe just because the organization happens to be large. Each of these reasons treats methodology selection as a matter of preference or convenience rather than a decision that should follow from the actual nature of the work. Methodology selection should be based on the work itself, the team doing it, the customer being served, and the broader organizational environment the team operates within.
If the work is complex product development with changing requirements, Scrum may be a strong choice, since its short cycles create regular checkpoints for feedback and adjustment. If work arrives continuously and unpredictably, such as support tickets or operational requests, Kanban may fit better, since it manages flow rather than trying to force unpredictable work into fixed planning cycles. If technical quality is the main risk, perhaps because the codebase is fragile or the domain demands high reliability, XP practices may be needed to build discipline directly into how the code gets written. If the organization needs strong governance around funding, compliance, or auditability, DSDM or Disciplined Agile may help bridge that gap. And if many teams must coordinate around a single product or platform, a scaling approach may be appropriate to manage the dependencies between them.
Before settling on an approach, it helps to work through a few grounding questions:
- Is the work predictable, exploratory, or a mix of both?
- Does work arrive in planned batches or continuously and unpredictably?
- Is technical quality or engineering risk the biggest threat to delivery?
- Does the organization need governance, compliance, or funding controls?
- Does delivery depend on one team, or on several teams coordinating together?
None of these questions has a single right answer that applies to every team, which is exactly why methodology selection has to be a deliberate exercise rather than a copy-paste decision. Answering them honestly usually points toward a method, or more often a blend of methods, that actually fits the situation at hand.
In practice, the best Agile teams often combine methods thoughtfully rather than picking just one and forcing every situation to fit it. A team might use Scrum for cadence, Kanban for managing daily flow, XP for engineering quality, Lean thinking for waste reduction, and scaling practices for coordinating with other teams. Combining methods like this isn't a sign of confusion or indecision. It's a sign of a team that understands its own context well enough to borrow the right tool for each part of the problem, as long as the choices are intentional and clearly support value delivery rather than being adopted for their own sake.
Common Methodology Selection Mistakes
One common mistake is choosing a method based on fashion rather than fit. An executive hears that Scrum is popular at other companies, so every team is told to adopt it, including teams doing support or operational work where Kanban would likely serve them better. This kind of top-down mandate skips right past the question of what the work actually requires, and it often leaves teams performing ceremonies that don't match how their work actually behaves.
Another mistake is choosing a method to avoid real cultural change. A company may adopt Agile roles and ceremonies, standups, sprint reviews, retrospectives, while keeping the same command-and-control decision-making underneath. Leaders still make all the calls, teams still wait for approval on basic decisions, and nothing about how authority or trust actually flows through the organization has changed. This creates what practitioners often call "doing Agile" without "being Agile," where the vocabulary changes but the underlying behavior doesn't.
Myth: A scaling framework will fix a struggling Agile rollout. Some organizations adopt a large scaling framework before individual teams have learned how to deliver value reliably on their own. Scaling weak Agile practices usually doesn't fix them. It just spreads the same problems across more teams and adds coordination overhead on top.
This is why experienced practitioners usually recommend getting the fundamentals working at the team level first: a healthy backlog, honest retrospectives, a team that can actually finish what it starts, before layering on a framework designed to coordinate dozens of teams at once. Scaling something that doesn't work yet just makes the dysfunction bigger and harder to see.
A fourth mistake is ignoring technical excellence entirely. Teams may adopt Scrum ceremonies enthusiastically, running crisp sprint plannings and reviews, while continuing to build fragile software with poor testing and mounting technical debt underneath. Ceremonies alone don't produce quality, and a team can look Agile on the surface while its codebase quietly becomes harder to change every sprint.
A simple way to think about closing this gap:
- Keep the Scrum cadence for planning and feedback.
- Add XP practices such as test-driven development and continuous integration.
- Track technical debt alongside feature work, not separately from it.
- Review code quality in retrospectives, not just delivery speed.
In this case, XP practices may be just as important as Scrum events, since a well-run sprint cycle wrapped around a deteriorating codebase only postpones the problem. Pairing a delivery rhythm with real engineering discipline is usually what separates teams that stay fast for years from teams that slow down right when the stakes get highest.
This page titled 3.2.4: Choosing the Right Agile Approach was last modified on Sun, 30 Aug 2026 18:40:10 GMT and is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by Guharaman Janakiraman.
The book could not be loaded just now.