DevOps is the New Black
The answer lies in DevOps, or more specifically, the integration of development and operations. According to Forbes magazine, DevOps, alongside Continuous Delivery, are among the latest celebrated approaches to faster software and deployment (1). IT activities have typically been siloed, each within its own specialized functional area, with limited collaboration across the end-to-end development & delivery lifecycle (2). The result is a structure that is rigid and slow in response to unpredictable changing market demands. The resulting loss of productivity and efficiency is moving enterprise towards a more streamlined approach, which links both development and operations into one integrated process.
Enterprises that embrace DevOps are essentially emulating the practices of Amazon.com or Netflix, in which an e-commerce business could gradually improve their applications by pushing new code on a daily basis in comparison to longer, less agile and larger releases (3). Figure 1 demonstrates the cross-interest in development and operations.
Together, DevOps and Continuous Delivery link the incremental aspects of agile software development to the operations of software deployment (5). The end result of a smoothly integrated DevOps framework is a more agile response to the market and to your end consumer, but DevOps is highly focused around both people and culture. Therefore, we see culture as the largest barrier to integrating DevOps as culture within organizations is resistant and hardened, making it terribly hard to integrate an idea that goes against traditional enterprise models.
As seen above, a traditional framework shows how 'desire for change' varies within different departments, resulting in adoption barriers. In order for DevOps to be integrated effectively, an organization's culture needs to have a consistent 'desire for change' across all departments.
Therefore, in order to improve the interaction between development and operations, there will need to be an uptake of new technologies and processes that can ruthlessly prioritize decision-making and facilitate collaboration (7). Platforms that allow for work and decision processes to strategically cross organizational boundaries will be needed to make sure that organizations adopt the practices that make DevOps both worthwhile and innovative. (8) In conclusion, the linking of development and operations into one streamlined process can have profound effects on both productivity and efficiency, but there needs to be a foundation laid before hand in order to allow for collaboration to cross such traditional organizational borders. If these boundaries can be overcome, DevOps will have the room to thrive.
1,3,5,8 Carr, D. (2015, April 5). Digital Enterprises Face DevOps Dilemma. Retrieved May 27, 2015, from http://www.forbes.com/sites/davidcarr/2015/05/04/digital-enterprises-face-devops-dilemma/
2 Lohmeyer, S. (2015, May 11). DevOps fears and the 'Dilbert effect' Retrieved May 27, 2015, from http://gcn.com/articles/2015/05/11/devops-cloud.aspx
4 How DevOps Brings Order to a Cloud-oriented World. (2011, March 1). Retrieved May 27, 2015, from http://searchcloudcomputing.techtarget.com/feature/How-DevOps-brings-order-to-a-cloud-oriented-world
6 Menzel, G., & Macaulay, A. (2014). DevOps - The Future of Application Lifestyle Application. Retrieved May 27, 2015, from https://www.capgemini.com/resource-file-access/resource/pdf/devops-thefutureofapplicationlifecycle_automation.pdf
7 Gardiner, B. (2015, March 9). DevOps to Become Mainstream by 2016. Retrieved May 27, 2015, from http://www.cio.com.au/article/569856/devops-become-mainstream-by-2016/