Creating value for the customer is essential in any business. You want to be sure that you are maximizing the value you create for them through your development process. The DevOps methodologies aim to build a fast and reliable software delivery process. When adopting this paradigm, you must reassess your existing process and look for inefficiencies.
One way to do this is by using Value Stream Mapping (VSM). This involves gathering people from all parts of the product development process, including the business line, design, testing, QA, operations, and support. Doing so can give you a clear picture of where value is being created and lost.
Value Stream Mapping is centred around a colour-codded map that describes your process and measures its efficiency as the ratio of value-added steps over all the steps of the process.
What is value stream mapping, and why is it important?
Value stream mapping is a useful tool for understanding how value is created and lost (wasted) in a product development process. This method was invented in the context of industrial engineering to make production lines more efficient and Lean.
By gathering people from all parts of the value stream, you can get a clear picture of which step in the process contributes to creating values and which are potential waste. Collecting this information can help you optimize the development process and provide a visual way to explain the process and why a step of the process exists in the first place.
In the context of Lean Manufacturing, Value Stream Mapping is an improvement Kata. An improvement Kata is an iterative process conducted by small and rapid experiments to improve an organisation’s process. The Value Stream Mapping methodologies are built around the four steps of the Improvement Kata:
- Discovery — Identify areas where you can improve the efficiency of your process.
- Understanding — Understand where value is being created and lost in your product.
- Experiments — Select and design small experiments to iteratively improve the processes.
- Change — Make better decisions about how to optimize the development process.