Preface

You run perfect sprint plannings. Your retrospectives surface great insights. Your daily standups stay under fifteen minutes. Your velocity is stable, your burndown charts are healthy, and stakeholders praise your “excellent facilitation.”

Yet nothing actually gets faster. Features still take weeks to reach customers. Dependencies still block progress. Quality issues still slip through. The organization still sees you as “the standup person” rather than someone who drives measurable improvement.

This book offers you a way out.

Not by abandoning Scrum—Scrum isn’t the problem. The problem is treating it as a ritual to follow rather than a tool to create flow. The solution is shifting from ceremony facilitation to value flow optimization, from measuring team velocity to measuring the time from idea to business impact, from focusing inward on sprint health to focusing outward on whether value actually reaches customers and achieves its intended outcome.

This shift isn’t a new role. It’s a new posture. I call it the Value Flow Manager—not because you need a title change, but because you need a different way of seeing your work.

This book will show you how.

It draws from a decade of coaching Scrum Masters and Release Train Engineers across aerospace, telecommunications, public sector, and entertainment industries. Every technique has been field-tested. Every metric has proven its value. Every example reflects real transformations—though names and details are changed to protect confidentiality.

You’ll follow three practitioners on their journeys:

Sophie, a Scrum Master working in the space industry, discovers that her team’s “two-week sprints” mask a reality where ideas take months to reach users and deliver measurable impact. She learns to measure actual flow from idea to business outcome, identify bottlenecks systematically, and cut delivery time.

Nicolas, managing three teams in the French public sector, realizes his teams are busy but not fast. Citizens wait months between requesting a service and actually using it. He shifts from coordinating ceremonies to eliminating organizational bottlenecks across the entire value stream—from citizen need to citizen impact.

Alix, a Release Train Engineer in aeronautics, orchestrates flow optimization across 80+ people in a value stream where regulatory compliance can’t be shortcut. Alix learns to see the full picture—from capability idea through delivery to operational impact—balancing safety requirements with delivery speed.

Their challenges will likely mirror yours. Their solutions will give you a roadmap.

This book is organized around practical progression:

• Part 1: The Reality Check — Understand why traditional Scrum practice leads to agile fatigue
• Part 2: The Paradigm Shift — Learn the Lean principles that underpin flow optimization
• Part 3: The Method — Master the core tools: Value Stream Mapping, flow metrics, improvement OKRs
• Part 4: The Transition — Navigate organizational resistance, build authority, sustain momentum

Read it cover to cover for the complete framework. Or jump to specific chapters for immediate problems. Either way works.

Before we jump together on the topic, one final note about how this book was created.

I wrote this book with AI assistance—specifically Claude Sonnet 4.5—and the experience became a perfect case study in Value Flow Management.

I started writing on December 16th, 2025. Parts 1 and 2 were released on January 13th, 2026—less than one month to first earned value. Part 3 followed on January 18th. The complete book was published on January 27th, 2026—just six weeks from start to finish.

To put that in perspective: I had just spent seven months writing a science fiction novel without AI assistance, not counting the years of idea maturation before that. And it’s still far from done. The contrast in lead time is striking (even if the purpose and market reality is different).

But let me be clear about what AI did and didn’t do.

Every idea in this book is mine. Every anecdote comes from my decade of coaching. Every opinion, every framework articulation, every technique—these emerged from my own practice, failures, and discoveries. Sophie, Nicolas, and Alix are composites of the dozens of Scrum Masters and RTEs I’ve worked with, coached, and learned from.

Claude’s role was to accelerate the translation of my expertise into written form. I would describe concepts, share stories, explain frameworks—and Claude would structure them into clear prose. I would then edit, refine, add depth, challenge assumptions, ensure technical accuracy.

Think of it as pair programming for writing. I brought domain expertise and strategic vision. Claude brought structural clarity and production speed.

What AI changed was the bottleneck. Instead of staring at blank pages for months, struggling to structure my thoughts, I could rapidly generate first drafts. But that just shifted the constraint—exactly as Theory of Constraints predicts. I spent one to four hours a day—over a month in total—refining every passage, verifying that generated content aligned with my actual thinking, reworking character consistency, and ensuring narrative coherence. Some chapters were rewritten three or four times because the tone didn’t feel authentic to me.

The math tells the story. Total elapsed time: 42 days (December 16th to January 27th). Total active work time: approximately 90 hours spread over those 42 days. Flow efficiency: roughly 9% (90 hours / 1,008 hours).

Even with AI assistance, 91% of the time was waiting—waiting for ideas to crystallize, for feedback to arrive, for clarity to emerge. Of course, I also have a job outside of writing!

But here’s what changed: My lead time collapsed from months to weeks, while my quality standards remained uncompromised. The bottleneck simply moved from content generation to refinement and validation. This is precisely what Sophie, Nicolas, and Alix will discover in their own journeys: when you optimize one constraint, you don’t eliminate work—you elevate it to higher-value activities. You move from “getting words on paper” to “ensuring those words truly matter.”

Of course, the goal wasn’t speed for its own sake. The goal was to release value as fast as possible and learn from feedback. That’s why I published on Leanpub—the platform allows unfinished books to be published at lower prices. Parts 1 and 2 released after 28 days. Part 3 after 33 days. And I expect more changes as I get more and more feedbacks. That’s Lean and Agile principles applied to the book itself.

This book isn’t just about Value Flow Management. It was created through Value Flow Management.

Now let’s get you moving from ceremony facilitation to flow optimization.

The transformation starts here.