Scrum vs Kanban debate misses the point: it's about promise size, not method

A software team working on a 10-month project cycled through three agile approaches — Kanban, Strong Ownership, and Scrum — without changing their core ceremonies or tooling. The only variable that shifted was what the author calls 'promise size': the scope of work a single person commits to, ranging from a micro-task to a full page to a story-point-based sprint. The team's choice of approach at each phase was driven purely by their level of certainty about the work ahead, not by coach recommendations or framework ideology. During the first three months, two methods ran simultaneously — developers pulled Kanban tasks while the lead architect worked under Strong Ownership — and no one found it unusual. The author argues that framing agile decisions around estimation granularity, rather than methodology labels, is a more honest and practical way to manage software projects.