Agile vs Scrum vs Kanban: How Small Development Teams Should Choose a Workflow
If you have ever sat in a meeting where someone said “we do Agile” and someone else answered “no, we do Kanban”, you already know the core problem with the agile vs scrum vs kanban debate: the three words do not belong to the same category. Comparing them directly is like comparing healthy eating with the Mediterranean diet and calorie counting. This guide is written for small development teams, typically 3 to 8 people, and especially for the 4-person squad that has to ship client work and product work at the same time. No theory for theory’s sake. We look at what each option actually costs you in meetings, roles and tooling, then we give you a decision path. The 30-Second Answer What it is Prescribes roles? Prescribes meetings? Best for Agile A mindset and set of 4 values / 12 principles No No Defining why you work the way you do Scrum A framework with sprints, 3 accountabilities, 5 events, 3 artifacts Yes (3) Yes (5) Scoped projects with a stakeholder who needs a rhythm Kanban A flow method layered on top of how you already work No Optional cadences Continuous product work, support, unpredictable intake The short version: Agile is the philosophy. Scrum and Kanban are two different ways of being Agile. You can do Scrum badly and not be Agile at all. You can do Kanban well and be extremely Agile. Agile: The Umbrella, Not the Method Agile came out of the 2001 Agile Manifesto. It says four things matter more than their opposites: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is it. There is no board, no sprint, no role, no ticket type. Which is why “we are Agile” is not an answer to “how do you work?”. It is an answer to “what do you value when things go wrong?”. For a 4-person team, the practical translation of Agile is simple: ship something a user can touch at least every two weeks, and be willing to change the plan based on what you learn. Everything else in this article is implementation detail. Where Waterfall fits in Waterfall is the contrast case: requirements, then design, then build, then test, then release, each phase gated. It is not evil. For a migration with a hard regulatory deadline and zero scope ambiguity, phase gates are honest. It becomes a problem when nobody knows the requirements yet, which is most software work. Scrum: What It Actually Requires Scrum is often summarised with the 3:5:3 rule, which is the fastest way to understand what you are signing up for. 3 accountabilities Product Owner: owns the backlog and the ordering of it. One person, not a committee. Scrum Master: owns the process, removes blockers, protects the sprint. Developers: everyone who builds the increment. 5 events The Sprint itself (1 to 4 weeks, usually 2) Sprint Planning Daily Scrum (15 minutes, every working day) Sprint Review (demo to stakeholders) Sprint Retrospective 3 artifacts Product Backlog (with a Product Goal) Sprint Backlog (with a Sprint Goal) Increment (with a Definition of Done) Concrete example: 4 people running Scrum Team: two senior devs, one junior dev, one full-stack lead who also wears the Scrum Master hat. The client’s product manager is the Product Owner. Two-week sprints, 80 hours of capacity per person. Here is what a sprint actually consumes: Event Duration Attendees Person-hours / sprint Sprint Planning 90 min 4 6.0 Daily Scrum x 10 15 min 4 10.0 Backlog Refinement 60 min 4 4.0 Sprint Review 60 min 4 4.0 Retrospective 45 min 4 3.0 Total 27 h out of 320 h (~8.5%) Roughly 8 to 9 percent of capacity goes into the process. That is the honest price of Scrum, and it is defensible if you get something back: a predictable demo date, a forced conversation about priorities, and a retrospective that actually changes something. It stops being defensible when the sprint goal changes on day 3 every single sprint. At that point you are paying for ceremony and getting none of the predictability. What goes wrong with Scrum on small teams Nobody is a real Product Owner. The client answers emails in 48 hours and the backlog rots. The Scrum Master is also the lead dev. Process work gets dropped first when a deadline hits. Estimation theatre. Four people arguing about whether something is a 3 or a 5 for 40 minutes. Interruptions break the sprint. Production bugs and client calls do not respect your timebox. Kanban: What It Actually Requires Kanban asks you to start with what you do now. There are no new roles and no mandatory meetings. What it does demand is discipline on a handful of practices: Visualise the workflow. Every real step gets a column, including the ugly ones like “waiting for client feedback”. Limit work in progress (WIP). This is the non-negotiable part. No WIP limits means you have a to-do list, not Kanban. Manage flow. Track cycle time and throughput, not velocity points. Make policies explicit. Write down what “ready” and “done” mean for each column. Improve collaboratively. Change the system based on flow data, not vibes. Concrete example: the same 4 people running Kanban Same team, same people, now on a long-running SaaS product with a steady stream of feature requests and support escalations. The board: Backlog → Ready (limit 6) → In Dev (limit 3) → Code Review (limit 2) → QA / Staging (limit 2) → Done. Why In Dev limit 3 with 4 developers? Because the fourth person is expected to unblock a review rather than start a fifth ticket. That single constraint is what kills the “everything is 90% done” syndrome. Their cadences: Cadence Frequency Person-hours / 2 weeks Board walk (right to left, 10 min) Daily 6.7 Replenishment meeting (30 min) Weekly 4.0 Flow review / retro (45 min) Monthly 1.5 Total ~12 h out
Agile vs Scrum vs Kanban: How Small Development Teams Should Choose a Workflow Read More »










