When any organization decides to take on the challenge of moving to DevOps, one of the very first orders of business for the DevOps leaders should be to hold a Value Stream Mapping exercise. One of the reasons why we want to start with a Value Stream Mapping exercise is to discover where we will start our DevOps implementation. Most organizations produce more than one software application, so we need a way to help us determine which application (pilot application) we will start with before attempting to scale across all the applications. It is generally not advisable to attempt to scale DevOps across all applications at once due to the fact that there is no such thing as DevOps in a box, which means there will be trial and error during the initial pilot project.
So, what exactly is Value Stream Mapping? Value stream mapping is a lean-management method for analyzing the current state and designing a future state for the series of events that take a product or service from its beginning through to the customer. Value Stream Mapping, has also been called other names, such as at Toyota, where it is known as “material and information flow mapping”. Value Stream Mapping can be applied to nearly any value chain (process).