Project to Product

Project to Product maps out a framework for transforming how software organizations deliver business value. The book introduces the Flow Framework™ as a method to measure and improve software delivery by focusing on business outcomes rather than technical metrics. Kersten draws parallels between software delivery and manufacturing's evolution during the Industrial Revolution, using historical examples to contextualize current challenges. Through case studies and research, he demonstrates how traditional project management approaches fall short in modern software development. The author presents concrete steps for measuring flow metrics, identifying bottlenecks, and optimizing value streams in technology organizations. The book outlines strategies for connecting technical work to business results while balancing security, quality, and customer value. The text advances a thesis that software development must evolve beyond project-based thinking to survive in the age of digital disruption. This core argument challenges established practices in enterprise IT and proposes a new model for organizational success.

Readers appreciate the book's concrete framework for measuring software delivery and connecting technology investments to business results. Many highlight the Flow Framework™ as a practical way to track work across different value streams. Common praise focuses on: - Clear metrics for measuring IT performance - Real examples from Nokia's transformation - Historical context linking manufacturing to software - Solutions for bridging business-IT disconnect Common criticisms include: - Too much focus on the author's experience at Tasktop - Repetitive concepts in middle chapters - Framework details feel incomplete/surface-level - Heavy emphasis on selling Flow Framework™ Ratings: Goodreads: 4.1/5 (1,100+ ratings) Amazon: 4.5/5 (300+ ratings) Several reviewers noted the book explains "why" better than "how." As one Amazon reviewer wrote: "Great at diagnosing problems but light on practical implementation steps for smaller organizations." Some readers found the manufacturing analogies overused, with a Goodreads review stating "the Ford/Toyota comparisons become tedious."

Team Topologies by Matthew Skelton, Manuel Pais This book presents organizational patterns for structuring technology teams to optimize flow and delivery in the digital age.

Accelerate by Gene Kim The authors use data and research to show how technology organizations can increase performance through specific technical practices.

The DevOps Handbook by Gene Kim, Jez Humble, Patrick Debois, and John Willis This guide provides technical and architectural practices to improve collaboration between Development and Operations.

Making Work Visible by Dominica DeGrandis The book presents methods to expose time theft and optimize workflow in technology organizations.

Lean Enterprise by Jez Humble, Joanne Molesky, Barry O'Reilly This work demonstrates how to transform technology organizations using lean and agile principles at scale.

🔹 The book was inspired by Kersten's meeting with Dr. Stephen Spear, who showed him how Toyota's approach to car manufacturing could revolutionize software development. 🔹 Mik Kersten created the Task-Based Development framework while pursuing his PhD at the University of British Columbia, which later evolved into the Flow Framework® discussed in the book. 🔹 The term "Project to Product" refers to a fundamental shift in how organizations deliver value, moving from temporary project-based work to long-lived product value streams. 🔹 The Flow Framework® draws parallels between software delivery and manufacturing principles used during the Industrial Revolution, particularly the work of W. Edwards Deming. 🔹 Kersten founded Tasktop Technologies after observing developers spending only about 30% of their time actually writing code, with the rest lost to coordination and communication overhead.