From the Blogosphere
Overcoming the Limitations of a Bimodal IT Strategy | @DevOpsSummit #DevOps #ContinuousDelivery
Understanding the pros and cons of bimodal IT strategy is essential to its effective implementation
By: Automic Blog
Apr. 5, 2017 10:00 AM
Overcoming the Limitations of a Bimodal IT Strategy
What Is Bimodal IT?
Of course this needs a little unpacking, but in essence Bimodal IT refers to the notion of two distinct areas of an IT department. Mode one must ensure the stability of the organisation and the success of the core business applications, while mode two is the cutting edge, focused on disrupting the industry.
Supporters of Bimodal IT argue the strategy has evolved naturally and reflects generational differences that characterize the two sets of employees. The workforce that has existed for upwards of 20 years and has the experience in legacy systems are often employed in mode one environments, whereas the younger developers more familiar with recent technology tend to work on disrupting the status quo and implementing new ideas.
What Are the Benefits?
Such a setup provides a significant amount of flexibility to the mode two developers, who are not constrained by older systems and tools. They can adapt to ever-changing and evolving technology stacks, enabling the company to stay at the cutting edge of any particular sector. Empowered with new tools and technologies, the team can work on delivering new solutions that will save the company money and increase engagement. Indeed, with disruption taking place across all industries, a lack of versatile and innovative applications could be the difference between success and failure.
With users constantly providing new challenges and placing demands upon the organization, it is much easier to focus on moving forward when you're not distracted with maintenance work. IT staff can instead deliver speed and innovation, testing new technologies without risking business continuity. With mode one team ensuring stability, the approach reduces the risk associated with full-scale deployment of new technologies and mitigates the effects of a full-scale transformation from legacy systems to new agile systems.
A knock-on effect is the removal of shadow IT. Because business users are getting the applications they need quickly, there is no need to bypass IT, which in turn helps to curb the use of unauthorized applications and software.
What Are Its Limitations?
However, allowing mode one to get cut adrift will result in a number of problems. No-one will want to work in this space and it will become a silo, increasingly isolated and gradually forgotten by the rest of the IT world. This will result in core applications becoming cumbersome and the future of mode one disregarded and bleak.
Moreover, the creativity, freedom and exploration afforded to mode two is not shared, resulting in a division between the two modes. If management focuses its attention to either mode unfairly, it can exacerbate divisions with one side or another feeling disenfranchised. This of course will lead to a breakdown in communication between the two teams that are already working towards different targets, with different ambitions and needs.
If the IT department becomes fractured and disharmonious, the implications can be severe. Those concerned with maintaining legacy systems may well create resistance to new technology within the workplace. This resistance may even spread to stakeholders. Such a state can lead to confusion with employees unsure of the company's direction and staff working in a mode unsuited to their skillsets or interests.
Of course the dwindling number of people with expertise in the mode one arena further enhances concerns about the sustainability of the bimodal model: very few recent graduates will have either the desire or relevant knowledge to work on legacy systems. This can create an imbalance in the size of the teams and also the cost - with mode one developers increasingly scarce, the fees they can command could skyrocket. For smaller companies that have difficulty in staffing a single IT department, the time and cost of sourcing a team that can be split into two to focus on different areas of work independently from one another is simply inconceivable.
How Do We Overcome These Restrictions?
Through Application Release Automation it is possible to connect release and deployment processes across different technologies. Automation and orchestration offer legacy system agility and new-age system compliance. Together they can overcome the current lack of control and end-to-end visibility and are hugely beneficial in complex environments, allowing business users and managers to track deployments and rapidly pinpoint issues when they arise.
Latest AJAXWorld RIA Stories
Subscribe to the World's Most Powerful Newsletters
Subscribe to Our Rss Feeds & Get Your SYS-CON News Live!
SYS-CON Featured Whitepapers
Most Read This Week