Built on lean thinking and systems theory, FLOW is a free delivery framework for software teams who want to ship more and meet less. No sprints. No velocity. Just work moving continuously from idea to delivered value.
2
Core documents
8
Core principles
∞
Delivery cadence
Sprint ceremonies cost the average ten-person engineering team approximately 7 hours per engineer per sprint, over $98,000 a year in recovered capacity. That is before accounting for the productivity loss of context switching, the dysfunction of velocity gaming, and the cultural pressure that keeps engineers from raising problems early.
As AI-assisted development accelerates the pace of code production, the gap between when work is ready and when a sprint allows it to ship is no longer just inefficient. Security vulnerabilities and AI-generated changes need to move from discovery to production in hours or minutes, not weeks. A sprint boundary standing between a critical fix and your users is a liability.
FLOW is a continuous delivery operating model and Agile framework built on lean thinking and systems theory. It replaces sprint commitments with pull-based execution, velocity with cycle time, and fixed ceremonies with meetings pulled only when there is something worth discussing.
One engineer, one board, one prioritized list. That is enough to start.
WIP, stage accountability, and aging are visible at all times. Decisions are made based on what is actually happening.
Work moves continuously from intake to delivery. Nothing sits idle. Bottlenecks surface immediately and trigger a corrective response.
Each stage has a clear accountability. When work stalls, the system tells you where it is and what needs to happen next.
Completing work in progress is always prioritized over starting new work. A partially finished feature delivers no value. Done delivers value.
The state of all work is visible at all times. Problems are surfaced as they happen, not discovered after the fact.
FLOW adopters take ownership of their stage and do not pass problems silently downstream. When something stalls, they name it.
Nothing moves forward without meeting exit criteria. Quality is not a phase. It is a gate at every stage.
When work stalls, those with capacity move to unblock it. Individual throughput is never more important than collective delivery.
Two documents. One for understanding the model. One for running it.
The research foundation for FLOW. Covers the operating model's origins, design rationale, and how it relates to Agile, Kanban, Scrum, and lean thinking. Grounded in established research with full citations. Intended for engineering leaders and decision makers.
The definitive guide to running FLOW. Covers stages, practices, accountabilities, artifacts, metrics, and adoption. The authoritative definition of the model for teams actively implementing it day to day.