Pick a methodology: Scrum, Kanban, XP, Lean or DevOps?

January 28, 2022
None of these items directly replaces or conflicts with any of the others. In fact, you can use them all simultaneously.

What’s the difference between Scrum, Kanban, XP (eXtreme Programming), Lean, and DevOps? How do you choose which one to use?

This is a common question I hear. Often asked just about two, but often the whole list. “Should my new team use Scrum or XP?” or “Which is better, kanban or lean?”

These questions come from a good place: Wanting to know how to taylor a tool/framework to a situation.

But as is often the case when you don’t know what you don’t know, asking an intelligent question is difficult.

The truth is, none of these items directly replaces or conflicts with any of the others. In fact, you can use them all simultaneously.

Here’s a super, over-simplified explanation of each, to point you in the right direction, if you’re considering which, if any of these, you should investigate further:

  • Scrum is about managing a team’s work
  • Kanban is about optimizing flow, or throughput
  • XP is about the particulars of software creation
  • Lean is about optimizing systems
  • DevOps is about promoting collaboration between developers, operations, and any other groups involved in product creation

Related Content

Scrum is great in theory, but "it will never work in the real world"

I think there are two "real worlds", and they often clash. One where Agile, Scrum, XP, and DevOps make perfect sense. Another where they don't.

How do I keep my devs busy while waiting on code review?

Don't worry about devs not having enough work. Worry on flow through the system.

Does Scrum make sense for a "DevOps Team"?

Scrum is about progressing toward the sprint goal. If you don't have a reasonable sprint goal because you're interrupt driven, maybe Scrum isn't right for you.