Tuesday, May 3, 2016
Why IT Delivery is like a Continuously Variable Transmission (CVT)
There is a great debate (overblown? perhaps ongoing dialog) among IT pundits and the IT community about "Bimodal IT".
If you are not familiar with Bimodal IT concepts, Gartner has a high level primer chart you can review here.
Is IT delivery undergoing a transformation? Is a Waterfall methodology primarily focused on reliability where Agile is focused on (duh) agility? Is Waterfall only inward looking, and Agile only customer experience centric? Of course these black and white extremes do not suit the complex topic of IT delivery. I've poked a little bit of harmless fun at the BiModal concept in the past, suggesting that TriModal or QuadModal is next on the horizon. I'll explore the evolution of IT delivery leveraging examples in comedy (and reality) of the razor industry, the audio industry and the auto industry as parallels.
For Saturday Night Live fans, it is easy to relate the current state of IT delivery to the SNL skit about the Triple Trac razor at a time when Gillette had just introduced the double bladed disposable razor. Like the razor industry, IT is an industry that thrives on change and on chasing the shiny silver ball. Who wants a double bladed razor when you can buy a triple bladed one, or a five bladed razor? Like the razor industry, IT delivery is ripe for disruption. Will Agile be the Dollar Shave Club of IT delivery to the Gillette Waterfall methodology? What as yet undiscovered IT delivery methodology will play the role of Harry's razors?
Not an SNL fan? The audio industry offers a similar story of evolution from stereo to quadraphonics (did anyone ever buy a quad setup?) to Dolby 5.1. Dolby 7.1 is now being eclipsed by Dolby Atmos which "frees sound from channels" and leverages a concept called "audio objects". I wonder if IT storage professionals find the audio industry evolution relatable to the move from JBOD to RAID to object storage? Will IT consumers / customers be able to appreciate the difference between a Dolby 5.1 sound (Waterfall) and Atmos (Agile)?
So what does any of this have to do with BiModal IT, or compare and contrast against Waterfall and Agile? IT delivery is always evolving and bright professionals are always in search of the next optimization. Concepts like BiModal IT are artificially limiting when there are more ways then ever for IT to provide business value and enhance the customer experience.
I really like cars, and could talk all day about almost anything automotive. As a result, some of my internal stories about IT invariably run into how IT and the auto industry are similar. IT delivery transformation is like the CVT, or continuously variable transmission. If you are not familiar with the CVT, rather than regurgitate, I'll refer you to Wikipedia.
What would the Waterfall methodology look like in a car?
To extend the car transmission theme, Waterfall would be like a manual transmission. Each shift point to a new gear could represent a "milestone" that represents a logical next step. While you could shift from first to fifth, you could lug the engine (miss your target date) or even stall (hit a significant roadblock). Your car runs most smoothly when you work the progression from first to second to third to fourth to fifth (and sixth if you have a nice sports car).
What about Agile?
Agile might be more like an automatic transmission. You've relinquished some control and in return you are expecting the car's computer (your scrum team) to make the best decision on what gear to be in based on your current speed (velocity). You may lose a little bit of gas mileage around town, and if you choose the right car (iteration planning), the automatic may hit 0-60 faster than a manual transmission (potential better outcomes from Agile than from Waterfall depending on the project).
Like a CVT, IT delivery is focused on efficiency (how many CIOs would be thrilled if their IT organization hit a metric, any metric that was 88% efficient?). A CVT can also adjust for greatest performance instead of efficiency. Because the CVT is "continuously variable", you are not necessarily locked into a set of specific progressions (Waterfall/manual) to meet a goal, or relying on adjustments along the way (Agile/automatic) to insure success. Where's the wrinkle? A CVT's strength is seamless change through an infinite range of "gears". The call to action for IT is not to be all one thing or the other, it is to recognize, adapt to and adopt change.
The velocity of technology ideas always outpaces our ability to deliver. Science fiction leads to science fact. Jules Verne wrote 20,000 Leagues Under the Sea, and in so doing invented the submarine long before one ever sailed the ocean blue. AT&T TV commercials in the 1980s demonstrated video chat. Skype and FaceTime are ubiquitous today. Technology professionals are passionate about their pursuits, particularly when it comes to how results are achieved. We all know in IT delivery there is no one size fits all or always right answer. It is exciting to see the passionate dialog about which IT project methodology is best, Waterfall or Agile. I believe in using the right tool (or methodology) for the job, and that both waterfall and agile techniques have their place, along with a number of other approaches that are either at present abandoned, unnamed or undiscovered. In order for IT delivery to provide the business value customers demand, we need to not lock into any one specific methodology, and like a CVT embrace seamless change that drives both efficiency and performance.
Subscribe to:
Posts (Atom)