Kanban vs Scrum: The Minimalist Project Management Framework

Scrum claims to be the smallest project‑management framework, but the author discovered in 2016 that Kanban is actually simpler; the Chinese translation of "Kanban" had misled many to think it was just a Scrum board.

Kanban consists of three core practices: visualize the workflow , limit work‑in‑progress (WIP) , and observe and improve the flow .

Because of this design, Kanban is simpler than Scrum and can be introduced into existing processes with little intrusion; even a pure waterfall team can define a Kanban board based on roles and steps, visualize delivery, limit WIP per step, create a pull system, observe flow, and improve bottlenecks without disrupting existing work.

Kanban focuses only on the number of parallel user stories in each stage and does not require estimation, unlike Scrum which demands sprint planning, story point estimation, and often inaccurate forecasts that consume significant effort and can jeopardize quality.

DevOps, as a blend of agile and lean, adopts many agile practices, but its project‑management side leans more toward Kanban’s pull‑based thinking.

Planning and execution are separate concerns; planning is an output, while delivery is the outcome. The author cites Luo Ji’s "The Usefulness of Planning" to emphasize that planning can be detached from the delivery process.

Although Kanban does not mandate daily stand‑ups, teams can still hold regular priority‑sorting meetings, daily stand‑ups, and retrospectives as needed.

Kanban boards without WIP limits are merely progress boards and do not achieve true pull; a pull system ensures that upstream only sends work when downstream capacity exists, prompting the Product Owner to prioritize tasks that maximize value.

Scrum and Kanban share many principles—both are rooted in agile and lean, aim to deliver value, eliminate waste, use pull‑based planning, limit WIP, rely on transparency for fast feedback, focus on early and frequent software delivery, and break large requirements into small stories.

In summary, the author distinguishes agile (Scrum) as "small steps, rapid feedback, frequent validation" and lean (Kanban) as "value focus, flow acceleration, waste reduction".

About the author

Agile, Lean, DevOps expert

Proficient in XP, Scrum, Kanban, TDD, CI, BDD, DevOps toolchain

Speaker at GDevOps, DevOpsDays Meetups

Author of "Cheetah Action: Agile Transformation in the Smoke of War"

Physical copies of the book are available on JD, Dangdang, Amazon, etc.; QR codes for purchase are provided below.

Follow the public account for more original works.

Upcoming DevOps+LIVE technical livestream details and registration information are announced, with a promotional poster included.