Author: David Coker, Vice President of Business Informatics at Intelligent Software Solutions (ISS)
As a developer of custom solutions for various public sector agencies, ISS has to be agile to remain competitive. We assessed adopting the much-discussed bimodal strategy of splitting the internal technology domain into two very distinct groups
1) The “legacy” group: traditional IT that’s focused on stability and efficiency. In the method endorsed by some large tech analysts, this group (and their technology) is on cruise control and more or less waiting to be phased out.
2) The “future” group: DevOps focused on requiring new tools and processes that enable agile development and point the way to cloud-based processes and enterprises.
When we looked at these two choices in the context of our culture, processes, and strategies, we decided we needed a “third way”: multimodal IT. In short, it is a DevOps approach spanning the entire enterprise, with the recognition that each different piece of the enterprise is at a different place on the continuum and will move forward at a different speed (crawl/walk/run). The result is a dynamic, on-premise environment that supports flexible, timely, and relevant capabilities while adhering to a wide range of compliance challenges.
How did we arrive at this approach? There were a number of key considerations.
DevOps Approach Spanning the Entire Enterprise
Thus, we made the decision to try to take everything forward to the future, realizing that different systems will move toward the agility horizon at different rates. However, DevOps means many things to many people. In the next post, I will discuss more about our specific DevOps thrust as regards our multimodal initiative.