Planview-bloggen

Din väg till smidighet i affärsverksamheten

DevOps Teams, Agil planering för företag, Skift från projekt till produkt, Hantering av värdeströmmar

Project to Product – Value Stream Metrics

Publicerad Av Tasktop Blogger
Project to Product – Value Stream Metrics

The review of Project to Product continues from Value Stream Management with the Flow Framework™, with a focus on Value Stream Metrics to track the flow of business value in our software development lifecycle.

The Flow Framework™ is a new framework created by Mik Kersten, CEO of Tasktop. It helps us bridge business and engineering with a common language and create transparency and a feedback loop by embracing the Value Stream Metrics.

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

The Flow Metrics is based on the four flow items (features, defects, risks, and debts), which help us measure velocity of business value using measures that are meaningful to business and engineering – we are finally bridging the gap that frameworks such as SAFe and Scaled Agile have focused on.

Value Stream Flow Efficiency

The book covers these key aspects of Value Stream Metrics:

  • Flow Distribution – track the distribution of features, defects, risks, and debts. New products typically need a larger set of features and non-production experiments usually have a low set of risks.
  • Flow Velocity – measure size of flow items delivered (pulled) by customers. Inherited from the Agile concept of velocity.
  • Flow Time – like cycle time, measure completed work from a flow items active to done state.
  • Flow Load – measures work in progress (WIP) to ensure we avoid over utilising the value streams.
  • Flow Efficiency – measures the ratio of productive to waiting time. It enables us to fine tine and optimise the value streams through a productivity lens.
  • Connect to Business Results – value, cost, quality, and happiness are the four business result buckets we can use to correlate investments with business performance.

Again, the book discusses invaluable case studies from BMW, Equifax, Nokia, and Microsoft, which links the value of the Flow Framework™ effectively with real-world examples. As others, we have tried a variety of dashboards and reports to connect the Ranger program with the business. Often in vain – as there is a gap between engineering, leadership, and our users.

Figure – Example dashboard that means everything to the Ranger engineers, but zip-zero to business ☹

Based on what we have covered to date, the Flow Framework™ would help us bridge the gap.

Looking forward to Part III of the book, which concludes with the Value Stream Network. It is the magic glue that connects the business with software delivery.

This blog was originally posted on Willy-Peter Schaub’s website.

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

Tasktop® and the Flow Framework™ are trademarks of Tasktop Technologies Incorporated.  

Relaterade inlägg

Skrivet av Tasktop Blogger