Agile
Post #523, on Aug 6, 2019 in TG
Scrum vs. Kanban: A Bi-Weekly Guilt Trip
Description
A screenshot of a tweet from Arturo Aguila (@churro777) with a dark background and white text. The tweet concisely states, 'Scrum is Kanban with a guilt trip every two weeks #scrum #agile @iamdevloper'. This meme offers a cynical yet highly relatable critique of the Scrum framework from a developer's perspective. It humorously distills the essence of Scrum down to its core difference from Kanban - the time-boxed sprint cycle, which often culminates in retrospective meetings where teams must account for unfinished work, hence the 'guilt trip.' This resonates deeply with senior engineers who have experienced the pressure and ceremony of sprint commitments versus the continuous flow model of Kanban
Use J and K for navigation
Comments
7Comment deleted
Kanban is a pull system. Scrum is also a pull system, but every two weeks you have to pull a convincing excuse out of thin air for the burn-down chart
Scrum: converting a perfectly healthy Kanban board into a fortnightly inquest on why 13 Fibonacci points refuse to fit inside 10 calendar days
After 20 years in tech, I've realized Scrum is just Waterfall with more meetings where we pretend the deadline isn't fixed while the PM updates the burndown chart to show we're "on track" despite everyone knowing we'll be crunching in week two
This perfectly captures the existential dread of Scrum practitioners everywhere: you're essentially running Kanban, but every two weeks you're summoned to a ceremonial tribunal where the team collectively reflects on why the velocity chart looks like a seismograph during an earthquake, why three story points somehow took five days, and why nobody updated JIRA. It's continuous delivery with scheduled emotional checkpoints - because apparently, we needed to formalize the guilt that comes naturally from shipping software
Kanban flows like a well-architected stream; Scrum dams it with sprint gates, flooding retrospectives with uncommitted backlog guilt
Scrum: Kanban where WIP limits are renamed “commitments” and every other Friday we apologize to velocity
Scrum: the variant of Kanban where WIP limits are replaced by fortnightly retros explaining why velocity refuses to be monotonic