The review of the PROJECT to PRODUCT book continues from Value Stream Metrics, with a tour of the value stream network based on a study of no less than 308 toolchains and three more epiphanies. To avoid the spoiler, you will have to read the book for the context and the profound impact of the latter 😊

The last part of the PROJECT to PRODUCT book shifts from WHY we need the Flow Framework™ to WHAT and HOW we need to track. It is pivotal that our business leaders and technologists articulate a taxonomy, a common business language, and metrics to measure the holistic success criteria.

Copyright © 2018 Tasktop Technologies Incorporated. All rights reserved. Published with permission.
Copyright © 2018 Tasktop Technologies Incorporated. All rights reserved. Published with permission.

It introduces the value stream network with three models – Integration, Activity, and Product. The Integration model supplies abstraction across tool chains, the Activity Model maps artifacts (tools) and interactions (specialists, teams) to flow items and value stream stages, and the Product Model aligns the flows and activities to products to enable us to measure flow metrics and correlating them to business results. I believe that when we, the ALM | DevOps Rangers, inspected our Azure DevOps (VSTS) Extension Work Streams, we focused on the integration and activity, but failed to consider the product. Instead of a Bridge too far, we went a Bridge to few.

After finally putting the book down, I was both excited 😊 and frustrated ☹

Excited as it will be able introduce a common business language and not just map, but also manage our value streams. We will be able to find excessive work in progress (WIP), unknown dependencies, unplanned work, conflicting priorities, and neglected ghost work. Frustrated as I was unable to take the Flow Framework™ for a trial run with one of our DevOps transformations that were on the verge of process explorations and value stream management.

Now to embrace the Flow Framework™ and evaluate its value with two real-world engineering teams moving from the ❶ assessment and ❷ people, to the ❸ process phase of “getting started” with DevOps. Let us see how we can bridge the gap between engineering and business with a managed value stream – watch this space!

Quick Reference Poster - DevOps Getting Started

References


The Flow FrameworkTM is a framework created by Mik Kersten, CEO of Tasktop Technologies Incorporated (“Tasktop”). The Flow FrameworkTMdiagrams, images, graphics and other materials referenced herein in relation to the Flow FrameworkTM is protected by copyright laws and may not be copied, modified or distributed without the express written permission of Tasktop.

Tasktop® and the Flow FrameworkTM are trademarks of Tasktop Technologies Incorporated.