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 […]
Tag: Technical Debt
Both Look Like a Sequence. Only One Expects the World to Change.
The Albatross Method vs. Waterfall: A Structural Comparison If you have read my description of the Albatross method, you may have had a reaction I hear often: “That looks like Waterfall.” I understand why. Albatross […]
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 […]
The Albatross Method as a Structural Fix for Tech Debt
This is a follow-up to Why Tech Debt Never Gets Repaid — It’s Not Visibility, It’s Incentives. That article argued the blocker is structural: the party responsible for delivery quality has no authority over the […]
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 […]