The DevOps Void & Value Stream Mapping
by Niall Crawford
After all, the company just invested “zillions” on a whole bunch of great tools and a cloud framework. Tools that allow you to automatically provision your infrastructure, applications, data and ensure that all your security obligations are met.
Hey! With this new” DevOps toolchain”, we should be moving our releases, from request to delivery, in a matter of minutes. You know … full push-button automation! … environments on demand! … And all that stuff!
Yeah! Right! But no! That’s not how it typically plays out.
In fact, a more realistic example might follow a storyline as follows:
- Project manager raises a request for a SIT environment.
- Request sits in it service management queue for a few days.
- Gets approved & assigned by test environment manager & distributed to engineering teams.
- Sits in the team ITSM queues for another few days.
- Apps team build the package in 5 minutes, but can’t deploy as infra not ready.
- Infra team provisions.
- Test team can’t start testing as data not ready.
- Data team provisions.
- Sorry, testing now too busy with another test cycle.
- Test teams spot a defect with the build.
- Higher priority project comes along and acquires environment.
- Go back to go.
I think one gets the point, the issue with DevOps efficiency is rarely the atomic task.
In fact (as illustrated in the diagram below), if you were to take a step back, you would probably realise the inefficiency is not in the operations themselves (like a build task) but in fact the “void” (or the wastage) in between.
In the above multi-process diagram, we can see the Data team takes:
- 180 minutes of operations (real value),
- 5 days of waiting (wastage),
- Or 2.5% Efficiency (Value Operation / [Value Operation + Wastage]).
Not exactly something you want to write home about. However, not an “untypical” in-efficiency, and a serious opportunity for improvement.
Imagine if for each team could move from 2.5% to just 25%. The benefits would be enormous, and over the lifetime of a project we could be saving weeks, maybe months, of time which translates to early “time to market” and significant IT project cost savings.
Enter Value Stream Mapping
Originally employed in the car manufacturing space, Value Stream Mapping (VSM) is a lean method that helps you better define a sequence of activities, identify wastage & ultimately improve your end-to-end processes. A set of methods that can be applied to any type of operation, including of course IT Environments & DevOps.
Wikipedia Definition: 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.
How do I go about implementing a simple* Value Stream Mapping for DevOps?
- Select the Product e.g. CRM application
- Select the Delivery Process of Interest e.g. Build a test environment
- Gather the SMEs, as VSM is a team event.
- Visually Map Current State (material flow / operational steps)
- Identify Non-Value between steps
- Add a timeline for both Operations (green line above) + Non-Value (red line above)
- Review Value Stream
- Design Future State (Optimize)
- Return to (3).
Tip: When getting started, steps 4 to 8 may initially be completed on whiteboards and simply use guesswork (in place of real data). However, for ongoing improvements, consider using tools that allow you to model your DevOps processes, track the operations and report on stream actuals. As an example, you could use the “Visual Runsheets Manager” functionality inside the Enov8 platform.
Benefits of DevOps Value Stream Mapping
- Baseline existing Operations
- Standardise Operations
- Identify Wastage
- Highlight Operational Bottlenecks *non-automated
- Lift Efficiency *continuous improvement
If you want to know more about how to leverage VSM in your IT Environment or DevOps world then feel free to contact team enov8. Enov8 is a complete solution to IT Environment & Release Operations and embraces VSM as a foundation capability in its overarching environments & operations platform. A capability that ultimately drives being “agile with discipline” or “continuous delivery at scale”.
Innovate with Enov8
If you are interested in learning more about IT & Test Environment Management and IT Release Management, contact us about EcoSystem.
EcoSystem is a fully configurable and easily integratable solution that comes with out of the box “enterprise management” functions that support IT & Test Environment Management, Release Management, Data Management, IT Operations Management, Configuration Management & Service Management.
Niall is the Co-Founder and CIO of Enov8. He has 25 years of experience working across the IT industry from Software Engineering, Architecture, IT & Test Environment Management and Executive Leadership. Niall has worked with, and advised, many global organisations covering verticals like Banking, Defence, Telecom and Information Technology Services.
19 MARCH, 2020 by Michiel Mulders SRE vs DevOps: Friends or Foes? Nowadays, there’s a lack of clarity about the difference between site reliability engineering (SRE) and development and operations (DevOps). There’s definitely an overlap between the roles, even though...
06 MARCH, 2020 by Arnab Roy Chowdhury Top 10 SRE Practices Do you know what the key to a successful website is? Well, you’re probably going to say that it’s quality coding. However, today, there’s one more aspect that we should consider. That’s reliability. There are...
20 FEBRUARY, 2020 by Arnab Row Chowdhury Technically, the world today has advanced to a level we never could’ve imagined a few years ago. What do you think made it possible? We now understand complexities. And how do you think that became possible? Literacy! Since...
14 FEBRUARY, 2020 by Michiel Mulders A site reliability engineer loves optimizing inefficient processes but also needs coding skills. He or she must have a deep understanding of the software to optimize processes. Therefore, we can say an SRE contributes directly to...
07 February, 2020 by Arnab Roy Chowdhury Do you remember what Uncle Ben said to young Peter Parker? “With great power comes great responsibility.” The same applies to companies. At present, businesses hold a huge amount of data—not only the data of a company but also...
17 JANUARY, 2020 by Sylvia Fronczak Site reliability engineering (SRE) uses techniques and approaches from software engineering to tackle reliability problems with a team’s operations and a site’s infrastructure. Knowing the history of SRE and understanding which...