Saying 'we do Agile' is the phrase I hear most often from clients who actually run daily meetings without any real change in how they work. Agile is a philosophy, not a method. Scrum and Kanban are concrete methods that implement that philosophy in very different ways. Confusing them costs time, money and project team credibility.
1. Agile: the mental framework, not the process. Agile is the set of values and principles of the Agile Manifesto (2001): people over processes, working software over exhaustive documentation, customer collaboration over contract negotiation, responding to change over following a rigid plan. It does not say how to organize sprints, who does what, or how to measure progress. That is why doing Agile without picking a concrete method is almost always organizational theater.
2. Scrum: when work is predictable and iterative. Scrum works when you can plan blocks of work (1-4 week sprints) with a clear objective and a prioritizable backlog. It is the right framework for product development, stable teams with defined roles (Product Owner, Scrum Master, Development Team) and contexts where the client can give feedback on a regular cadence. Scrum requires role discipline: if the Product Owner has no real decision authority, or the Scrum Master also acts as traditional PM, the framework collapses fast.
3. Kanban: when flow matters more than plan. Kanban works when work arrives continuously and unpredictably: customer support, operations, maintenance teams, or multi-project contexts with frequently shifting priorities. There are no sprints: there is a continuous flow with work-in-progress (WIP) limits per column. The key metric is not velocity but lead time (how long a task takes from entry to exit).
4. How to decide in 3 questions. Does work arrive in plannable waves or continuously and unpredictably? Waves means Scrum. Continuous means Kanban. Can the team isolate for 1-4 weeks on a shared objective? Yes means Scrum. No means Kanban. Do you need a deep cultural shift in roles, or just flow visibility and control? Deep shift means Scrum. Visibility means Kanban.
5. The hybrid model that works in practice. Many mature teams use Scrumban: Scrum sprint structure for planning, Kanban board with WIP limits for daily flow management. It is the approach I most often recommend to organizations with mixed teams (dev + support) because it does not force the entire company into a single rigid framework.
FAQ. Can I switch from Scrum to Kanban mid-project? Yes, and it is more common than expected: the signal is when sprints are constantly interrupted by urgent external requests. Do you need certification (PSM, CSM) to apply these frameworks? Certification helps with common language and stakeholder credibility, but does not replace hands-on adaptation experience to the specific context.
If your team says they do Agile but something feels off, let us talk: in a 30-minute call I will help you understand which framework really fits your context — without selling you a pre-packaged methodology.
