Tension. It can be uncomfortable, disconcerting, even a bit scary.
But it’s not unusual for the team supporting your digital infrastructure (IT) and your team developing new applications and refining legacy apps (software engineering) to exist in a state of tension at the best of times. Cloud migrations can heighten this tension to the extreme.
The needs and wants of Engineering and IT often come into conflict during a cloud migration. What’s more, the heightened tension can linger around long after the migration is done. That’s not just unpleasant. It can seriously impact your bottom line. So how do you mitigate the tensions between IT and Software Engineering?
Embracing DevOps methodology is a good way to move toward a world where Engineering and IT are seen as two parts of a more cohesive whole. This might require significant change in your organization. But the cost of complacency can be much higher.
Embracing DevOps methodology is a good way to move toward a world where Engineering and IT are seen as two parts of a more cohesive whole.
Understand IT Tension
Common causes of IT tension include:
- Conflicting Missions
The distinct missions of IT and Engineering can put them instantly into conflict. Engineering is focused on innovating and getting new applications out on time. IT is focused on providing a stable and secure environment for everyone from accounting to the front desk. So, while Engineering is one of many balanced priorities for IT, they believe they should be the top priority. This belief isn’t entirely unjustified. Satisfying clients and developing software are first on the list of Agile Methodology for a reason.
- Lack of Communication and Understanding
Different missions, scopes, and priorities can make communication difficult even during the best of times. In some cases, there may not even be enough of a shared language for communication. Disputes between IT and DevOps are often communicated and “negotiated” through third parties, adding further opportunity for creating tension. Lack of communication frequently leads to the blame game when things go wrong. This, in turn, deepens mistrust and animosity between the two departments.
Interdepartmental animosity between IT and Engineering doesn’t have to be a fact of life. Management can take steps to move two adversarial departments onto the same page. There might still be rivalries, but that can be healthy. Rivalries that are tempered by mutual respect inspire harder work and greater creativity. Organizations capable of this level of honesty, self-awareness and accountability, will gain a significant competitive advantage over those that are not.
This is the first post in a series of three that discusses the benefits of moving to a DevOps methodology. Next time (Defusing the Tension) we’ll explore some of the ways DevOps can address and defuse tensions within IT departments.
Robb Allen is the CEO of effectual, Inc.