Assess your agent harness for outcome orientation, trustable output, and continuous improvement. Extend spec-driven development through the product lifecycle.
Flow metrics aren't useful because metrics are good. They're useful when important work is slow, blockers show up late, and forecasts keep missing. Agentic development made all of that sharper, and your agents can be taught to watch for it.
Starting numbers for active work and queues, covering solo and multiplayer spec-driven development, pod topology, flow buffers, and replenishment cadence.
The real magic of spec-driven-development frameworks is how they make the code of the system running the agentic/human development lifecycle explicit, and opens the door to evolving this code to coach agents and humans towards more effective choices much more effectively than ever before.
An AI coaching prompt from my "Product Orientation Through LPM" talk: pressure-test one real initiative, find the real gap, and get one experiment to run.
Season 1 of Breaking the SAFe: where SAFe helps, where it goes sideways, and how to course-correct before the framework becomes theater.