Flight Execution
Running bounded delivery cycles that end with committed work shipped.
A program that delivers without bounded cycles loses the ability to commit; one that has cycles but does not honor them loses trust. Flight Execution runs cycles that are both bounded and honored.
Start here
Core tasks
Cycle planning
Review the upcoming backlog, estimate, and commit to a specific set of delivery units.
Daily synchronization
Short, focused coordination among active roles on what is in-flight and what is blocked.
Progress tracking
Maintain visible state on which delivery units are in what state, so blockers surface quickly.
Cycle review
Demonstrate what was produced and evaluate what was not — without blame and without narrative.
Retrospection
Identify one or two process improvements to apply to the next cycle.
From knowing to running
Knowing SPEED and running it are two different things. When you're ready to practice the methodology inside a program that runs it, the implementor path is where you begin.
Begin the implementor path