Scrum vs Kanban vs ATMOS: choosing the right framework for an SME

"Scrum or Kanban?" comes up every time an SME considers becoming more agile. It is often the wrong question. Scrum and Kanban were designed for software product teams. An SME of 40 to 200 people also has sales, finance, operations and HR teams. Forcing Scrum onto all of them produces an organization that holds ceremonies without becoming more responsive. Let's compare the three approaches honestly.

Scrum: a product framework by default

Scrum defines roles (Product Owner, Scrum Master, team), events (sprint planning, daily, review, retro) and artifacts (backlog, increment). It is effective for delivering a product in short iterations, when a prioritizable backlog exists. Strengths: inspect-and-adapt discipline, sprint-level predictability, product focus. Limits: assumes a PO who arbitrates, a stable backlog, and work that can be sliced into stories. Does not apply as-is to sales, finance or HR teams.

Kanban: a flow system, more flexible

Kanban focuses on visualizing the workflow, limiting work-in-progress (WIP) and continuously improving throughput. No sprints, no imposed roles. Strengths: gradual adoption without breaking the organization, applies to operational teams, surfaces bottlenecks. Limits: does not address shared Vision or cross-team alignment. Remains a team tool, not an organizational framework.

ATMOS METHOD: an organizational framework

ATMOS METHOD does not position itself as a team-level alternative to Scrum or Kanban. It is a framework above them, at organization scale. The V.I.S.I.O.N. Model structures six linked dimensions: Vision, Inputs, Systems, Interactions, Offer, Numbers. The C+1 principle guarantees every actor is at most one step from the customer, and that every operational decision stays tied to the Vision. Within that frame, a product team can perfectly use Scrum, a support team can use Kanban, and a sales team can run differently. ATMOS defines overall coherence.

Decision table

| Criterion | Scrum | Kanban | ATMOS METHOD |

|---|---|---|---|

| Target scale | Product team | Operational team | Whole organization |

| Work slicing | Fixed sprints | Continuous flow | Per function |

| Imposed roles | Yes | No | No |

| Addresses Vision | No | No | Yes (V pillar) |

| Addresses customer | Indirectly (PO) | No | Yes (C+1 principle) |

| Applies to finance/HR | No | Partially | Yes |

How to choose

If you are a single product team: Scrum or Kanban will do, based on your culture. If you are a multi-function SME aiming for real agility: neither addresses your problem. You need an organizational framework like ATMOS METHOD, inside which each team will pick its execution practices.

Three actions for this week

1. List your teams by type: product, operational, cross-functional. Note the current framework of each.

2. Spot uncovered zones: teams with neither Scrum, Kanban nor anything else. They are often agility blind spots.

3. Ask the coherence question: who guarantees these teams pull in the same direction? If the answer is "no one formally", that is where your transformation actually plays out.

To go further, discover [the V.I.S.I.O.N. Model in detail](/en/atmos) or [how ATMOS deploys concretely](/en/implementation).