As IT organizations respond to business demands that they rapidly scale support for faster application delivery, better security, and better reliability across the entire application portfolio, they are examining every aspect of their business processes, culture, and toolsets.

Systems that functioned perfectly well in the days when it took weeks to acquire, rack, and provision new compute resources are often poorly adapted to operations at cloud speed. The DevOps movement is a response to the opportunity the cloud provides to develop and deliver applications—with all their business benefits—to market faster. While the word DevOps is a concatenation of Developer and Operations, the DevOps movement sprang primarily from the developer side of the house, with faster application delivery as its primary mission. Operations teams, under pressure to ensure the security and availability of mission-critical applications, have often struggled to keep up with developer demands.

However, that doesn’t mean the two sides are necessarily in conflict. F5 surveyed over 800 NetOps and DevOps professionals to understand differences in how teams structured around distinct objectives perceive the priorities and contributions of other teams. What we found was encouraging: respect for each other’s priorities, mutual appreciation for the importance of automation, and a clear desire for more collaboration.

In order to read the detailed findings, download this whitepaper using the below link...