Kanban Can Run Bad

Kanban can run bad. Not straying away from being a Kanban, but running straight into a strangling mess. That’s the part people miss. Kanban doesn’t just let bad work through. It produces it. A card […]

Why Scrum Has Sprints

Scrum does not support parallel development of features. Not because it forbids it. Anyone can split a team across two features. It’s that Scrum gives the team no way to know whether the split is […]

Why Agile vs. Waterfall Is a False Choice

Every sprint is a mini-waterfall. Every Kanban board is a view of Waterfall’s middle phases. The debate assumes teams chose either Agile or Waterfall. Most teams are running both — and the methods don’t describe […]

The Albatross Method: The Next Generation of Agile for Long-Run Software

Most software does not get built once. It gets built, shipped, used, and then changed—for years. The frameworks the industry has relied on—Scrum and Kanban—were designed for prototyping, exploration, and iteration that can be reset […]

Why Tech Debt Never Gets Repaid — It’s Not Visibility, It’s Incentives

Every article on technical debt prescribes the same treatment: make it visible. Track it. Put it in the same system as features. Dedicate sprint time to it. Map where friction is worst. The assumption running […]

Estimation and Scheduling in the Albatross Method

As argued in It’s Time to Rethink Agile: The Albatross Method Is the Advanced PM’s Choice, it is time to rethink Agile. This article focuses on one part of the Albatross method — how it […]

Stripping Off the New Clothes of Kanban’s Work-Amount Prediction

A short fable about a method that produces confident numbers and calls it rigor. There’s an old story about an emperor who is sold a suit of clothes so fine that only the wise can […]