Project to Product: How to Survive and Thrive in the Age of Digital Disruption with the Flow Framework Paperback – Illustrated, November 20, 2018

DevOps guru Gene Kim rightly introduced this book with, "Every decade there are a couple of books that genuinely change my worldview. ... This is one such book."Mik Kersten provides ample evidence that the project and cost center orientation of so many software producing companies doesn't fit the Age of Software, and suggests a way becoming product-centric via a focus on value flow. The book is a an appealing combination of real-world examples of those who got it right (and who didn't) and practical explanations of what needs to be done to build measurable value networks.Net effect for me? A mind that is racing on how best to distill it into something I can evangelize in my workplace. This isn't a "single read" type of work, and extra kudos to Kersten for the useful glossary and extensive index.Get the book. Your company's future may depend on what it'll bring to light.

Lean concepts and flow can either tremendously improve software development and delivery or be horribly misapplied and wreak havoc. Most misapplication tends to come when project and mechanistic thinkers refuse to change their models of efficiency and production. This takes the rather obtuse work of Reinertsen in Product Development Flow and makes it much more approachable, applicable, and measurable. I would read Lean Enterprise first to get context; I would also suggest reading Escaping the Build Trap to get a more holistic understanding of "features" and product thinking. While the Flow framework itself is fairly straightforward, the potential for project and manufacturing thinkers to misapply the model to the detriment of the company and customer is very real; I have experienced this first hand in my current company.

This book has good content and very interesting when author used BMW plant as the reality and realize technology and DevOps/Agile methodology that are integrated in manufacture. Real scenarios/cases in this book very clear and author used fair-way (not criticize) to CIO/CTO or C-levels that were not aligned tendency.In this book, Flow Framework and 3 zones of Moore are the main contents, however, at last I don't find the mapping or anyway to integrated project to product in software (author said it can't) but this book is very useful for DevOps and any company applied Agile/Scrum to operations.One-size-does-not-fit-all, this book only show some cases in (digital) transformation and sometime making disruption such as Telsa or Uber.Note: if you had Make work Visible, A seat at the table, Phoenix Project...you have got a little as desired.

This book is packed with insights, real-life examples, and common issues that most of us in the software delivery had to deal with at some point in our careers. Although the book doesn't offer a technical or tactical guidance on how to switch to value-stream KPIs, it is a great starting point to shift the enterprise mindset on what matters the most, the alignment on how to define, map, and measure business results.I'd highly recommend this book to anyone who is interested in value stream management and large scale/strategic solution delivery initiatives.

This book is extremely important for anyone playing a role in transforming how your organization works. We are moving beyond the industrial and manufacturing age into a world that is powered by technology. Understanding how to restructure an organization around business value and create visible links to where business activity links to that value is critical. And it has to be done with a specific focus on how technology and software development drives business value.

I jumped into this book with a lot of excitement and the first few parts hinted at a finale that never came. It may just be my preference but it’s no use coming up with new terminology with academic writing if you don’t provide a concrete roadmap.If you are coming from an organization with no focus or a separate in-house development group outside your products, this book is illuminating. It provides a more academic style to example books like the Phoenix or Unicorn project books but the author does have a great way of relating stories and the sources of many of the ideas.At the end, it says “ this book does not provide details”. This is unfortunate because after going through the three parts, enjoying the stories of the successful and unsuccessful manufacturing companies, there is no “setup for success” It simply says “ here’s the concept - it’s up to you to figure out specifics”. That may work for some people but the great concepts put forth in the book needed just a little bit more of a nudge to take it over the finish line.

An insightful perspective of how to architect your software release cycle based on the value stream from strategy definition till it gets to the hands of end users, based on the capacity to visualize the value generated in each step and with it better been able to take decisions of how to improve it and where, using LEAN methodolgies.

Very insightfull. Real eyeopner. Love it