AI Made Coding Faster. Why Is Delivery Still Slow?
As AI-assisted development removes one constraint, most organizations will discover the bottleneck is somewhere else.
AI, Flow
Uncategorized
A Flow-Based Approach to Agile Transformation
About a year ago I wrote an article that presented Agile transformation as a fairly conventional iterative change program. Traditional
Flow, PI Planning, SAFe
Beyond PI Planning
PI Planning is a key event in the SAFe Scaled Agile Framework where multiple development teams—an entire Agile Release Train
Agile Planning, Flow, PI Planning
The Physics of Software Delivery: Why Certainty Is an Illusion
Why Software Delivery Is More Quantum Than You Think In quantum mechanics, we can’t predict exactly where a particle will
Flow, Kanban, PI Planning, SAFe
From Status Reporting to Flow-Based Control
From Status Reporting to Flow-Based Control Most ART Sync meetings don’t control delivery. They report on it. And that’s the problem. Agile
Flow, Kanban, PI Planning, SAFe
Probabilistic Feature Forecasting vs. PI Planning
Probabilistic Feature Forecasting vs. PI Planning Executives want a simple answer to a simple question: “What can we commit to
Flow, Kanban
From Batch-Mode Delivery to Continuous Flow
From Batch-Mode Delivery to Continuous Flow It’s been more than 2 decades since the Agile Manifesto, but many organizations are
Leadership, Scrum
Why Certification Alone Doesn’t Prepare Someone to Be a Scrum Master
This is a continuation of my previous article: The Leadership Model Every Scrum Master Should Know One of the reasons
Leadership, Scrum
The Leadership Model Every Scrum Master Should Know
Many Scrum Masters struggle with a subtle but persistent leadership dilemma: Should I focus on protecting the team — or
Agile Transformation, Business Agility
Agile Economics 101
The Economic Case for Agile vs Waterfall Waterfall Is a Large, Irreversible Capital Bet Traditional waterfall delivery: Commits significant capital
Flow, Kanban
Setting Initial WIP Limits
Starting Point: Team Size as Initial Upper Bound If team size = 5: A reasonable initial WIP cap is: WIP
Flow, Kanban
When Work Ages: Block It or Remove It from WIP?
When a work item starts to age beyond expectation, teams often face a practical question: Should we move it to
Flow, Kanban, Scrum
QA as a Separate Workflow State Breaks Flow
QA as a Separate Workflow State Breaks Flow Many teams still model testing as a distinct workflow state. Work moves
Flow, Kanban
What an Aging Breach is Telling You
What an Aging Breach Is Really Telling You In Kanban systems, aging is often misunderstood. Teams notice work items getting
Flow, Kanban
Kanban as a Control Plane for Knowledge Work
One of the most common misunderstandings about Kanban is that it is a way of doing the work. It isn’t.
Flow, Kanban
The One Rule That Makes Kanban Work
Kanban is often explained as a collection of practices: Visualize work.Limit WIP.Manage flow.Improve continuously. All of these are correct.None of
Flow, Kanban, Scrum
Flow-Based Agility vs. Timeboxes
Flow-based agility (e.g., Kanban) and timeboxed agility (e.g., Scrum) represent two distinct approaches to managing work. The primary difference lies
Flow, Kanban
Lean Principles Revisited
Lean Principles Revisited: Why Kanban Is a Control System Lean principles are widely taught, widely cited, and widely misunderstood—especially in
Flow, Kanban
Why Stop Starting is Hard
Why Stop Starting Is So Hard If there is one behavior that undermines flow more than any other, it is
Flow, Kanban
Kanban as a Flow Control Protocol
One of the most persistent misunderstandings about Kanban is the belief that it is primarily a visualization technique. Boards. Columns.