I may finish “Value Stream Mapping” by Karen Martin and Mike Osterling by the end of this commute.

Before DevOpsDays Toronto this year, I had no idea what Value Stream Mapping was about, but I had a notion it might be useful for our organization, based on details from “Accelerate” by Forsgren, et al.

Now that I know a lot more, I still feel it might be useful, but also sense that implementation is not for me. I’m not at management level, and am too close to the problems to facilitate.

I’d love to contribute to such an effort, but I’m just consciously acknowledging my limitations. If I want the benefits of such an effort in our company, the best things I can do are encourage and support.

@nbering I hadn’t heard of it before. I’ll have to read about it.

@jerry In summary, it’s a way of mapping - at a high level - how an organization gets from a request for products or services to delivery of that value (and beyond that to payment if billing comes after), to help reduce lead time and reduce waste.

Working at a high level instead of at the process level (where I work) helps get leadership buy-in.

The theory comes from Lean, and has developed from Toyota’s flow visualizations.

@jerry I originally looked into this because it’s the “missing piece” for Lean management practices in software companies. Efforts like work-in-progress reductions alone do not drive software delivery performance. But along with visualization tools to help inform decision-makers of how work is flowing through the system, Lean management does have a statistical impact.

@nbering ah. I may have forgotten the name for it. It would probably help my company, but I think it’s probably too big.

Sign in to participate in the conversation
Infosec Exchange

A Mastodon instance for info/cyber security-minded people.