Parts I and II are intentionally written in a minimalist manner so that they can serve as a small guidebook. This Part goes into greater depth for several of those chapters.
Value Stream Wide
Inherent Problems at Scale. It is important to recognize the problems of getting multiple teams to work together.
Mapping Your Value Stream. Value Stream Mapping is an activity that catalogs the steps in the work producing a product or delivering a service. It reveals where the interfaces are between activities, as well as the times involved in and between process steps.
Laws of Software Development. There are many concepts that are tantamount to laws in software development. Many of them relate to the creation of software, principles of flow, and organizational development. While software based product development cannot be reduced to a formula, understand these laws, principles, etc., is very important.
The Value Stream Impedance Scorecard. The Value Stream Impedance Scorecard (VSIS) is a qualitative method of determining if a change to your system will be an improvement or not. It is used to predict whether a speculated “to be” state will be an improvement over the current “as is” state. It does this being guided by whether or not the change will improve value realization. Essentially it looks to see if the resistance to flow will increase or decrease. The VSI Scorecard should be used as a heuristic as change in complex systems is not predictable although it can follow patterns.
Two online FLEX courses are now being offered – FLEX for SAFe, and Adopting FLEX (the first course in becoming a FLEX trainer).
If you want to learn about how to adopt FLEX in your organization please contact the author, Al Shalloway.