Value Stream Mapping (VSM) allows for a quick visualization of value being realized out of a work being executed. The good thing about VSM is it provides visualization to both the teams as well as the business sponsors to understand and plan for the go to market strategies easily. The value streams are usually a long-lived series of product or system development process that provides continuous flow of value to both the business and the customers. Not only Value Streams can provide visualization for the product / system development but also can be used for identifying the bottlenecks within the process and eliminate them to enable faster development.
However, there would be a few challenges while identifying the value stream when scaling up the agile at an enterprise level. At team level, when done effectively, even scrum boards or retrospectives can act as value stream mapping activities. A few techniques I have worked with that have been effective in identifying and ensuring flow of value are:
- Visualize – Come up with a conceptual diagram of the value stream that covers all the layers of the business unit / organization
- Milestones – Identify the milestones on the calendar when the values will be realized and how for both the business and the customer
- Measure – Have a measurement system in place to measure the waiting time, actual time and delays if any
- Retrospect – Observe and identify bottlenecks to streamline the value that needs to be delivered
I will discuss each technique in detail in my subsequent blogs.
Very well said, (NVA) non value adds and waiting time can be addressed in a easier way.