A large gap exists between what technologists have learned about effective software delivery and how businesses approach software projects. While DevOps and Agile principles have made a significant impact on how technologists work, they’ve been overly technology centric and have not been adopted broadly by business stakeholders. To bridge the gap, we need a framework that spans the language of the business and the language of technology and enables the transition from project to product. We need that framework to scale the three ways of DevOps—flow, feedback, and continuous learning—to the entire business. This is the goal of the Flow Framework.
Drawing on two decades of research and examples from Nokia and a top-25 bank, Mik Kersten explains why transformations at large organizations have failed and demonstrates how the Flow Framework enables organizations to survive and thrive in the age of digital disruption.
Mik Kersten spent a decade creating open source developer tools before realizing that programing was not the bottleneck of large-scale software delivery. Since that time, he has been working on creating a model and tools for connecting the end-to-end software value stream. He’s the CEO of Tasktop, where he helps IT leaders transform how software is built. He has been named a JavaOne Rock Star speaker and one of the IBM developerWorks Java top 10 writers of the decade. He was selected as one of the 2012 Business in Vancouver 40 under 40 and has been a World Technology Awards finalist in the IT Software category. Mik is the editor of the IEEE Software Department on DevOps. He created the Eclipse Mylyn open source project as part of his PhD in computer science, pioneering the integration of development tools with the delivery pipeline.
©2019, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org