E-mail :

To take on any new methodology or approach can be daunting and there is always a fear that you have gone out and acquired all necessary approvals and budgets – but what is this does not work?

Lets start off by looking at the benefits of DevOps. Perhaps a summarised view below from key papers written on actual implementations may help ease the fears, noting that they are realised on both aspects that are tangible around reduced cost and ability to ramp up delivery but also on the softer side of team dynamics and collaboration improvements. These aspects speak to the heart of all sizes of organisations and if in synch always end up being positive drivers for long lasting change that leaves a recognisable mark – that is not a stain or blemish but one that is referenced in a positive way for years to come.

Referring to the graphic below, Humble, et al. wrote a paper around the giant H.P. and Elliot on the IDC around their use of DevOps and how it greatly assisted them.

Rana et al. wrote more around the softer aspects and how it positively impacts team dynamics

In a further paper written by Krusche et al. in 2014 the writers speak to the key component of continuous delivery increasing the feedback loop and in turn communication between developers and customers is shortened – with an end result of far greater ‘on the mark delivery’ to clients. This means a happier client, happier staff and increased delivery across the board.

Ericka Chikowski a freelance journalist summed up her view on the benefits of DevOps neatly and has a white paper available to view at

Ericka’s paper in interesting in that it focuesed on the deeper gainings and benefits of DevOps by relating a gain in software quality and the resultant impact not only to R.O.I. but to the success of the projects as well as increased adoption and use of what has been developed.

Practitioner publicly available information from Cap Gemini and CIO insight speak to realised benefits that are measurable to executive committee members on decreased outages and reduced spending – seen below.


Looking at Gartners predictions one would note that they are pretty adamant that the DevOps methodology is going to pickup and be used more extensively in the future to realise the benefits being spoken of. If one takes into account that the key players in the market that link trends to actual implementations are stating that DevOps is here and definitely a view that organisations are looking at adopting and or are already in the process of adopting then i would believe that you are in safe territory for going down the road to start a journey of DevOps.

It is however prudent to also know some of the key challenges practitioners have found that you may reference and prepare for in advance.
Some of the noted challenges researched can be summarised into Devops being an approach that needs focus on a social and cultural level within an organisation with high risk but great reward. Having an inability to collaborate would be a non starter and the fact that you need to bring about change at a process level according to Gartner with people involvement is what makes this challenge something one must not undertake lightly.


Sources for reference on the benefits:

  • Krusche, S. and Alperowitz, L. 2014. Introduction of Continuous Delivery in Multi-Customer Project Courses. ACM 978-1-4503-2768-8/14/05.
  • Humble, J. and Kim, G., 2013. DevOps Culture and Practices to Create Flow. International software development conference.
  • Elliot, S., 2014. DevOps and the Cost of Downtime:Fortune 1000 Best Practice Metrics Quantified. IDC White Paper 253155.
  • Rana, R. and Staron, M., 2016. First International Workshop on Emerging Trends in DevOps and Infrastructure. ACM 978-1-4503-4134-9/16/05.

Sources for reference on the Challenges:

  1. Erich et al. 2014 – it’s an approach
  2. Jones et al. 2016 – as much a social and cultural phenomenon as it is a technical one
  3. Feitelson et al. 2013 – risk of rapid deployment but vital to maintain competitive advantage
  4. Mahanta et al. 2016 – inability to collaborate being a key non-starter
  • Erich, F., Amrit, C. and Daneva, M., 2014. Cooperation between Information System Development and Operations: A literature review. ACM 978-1-4503-2774-9/14/09.
  • Jones, S., Noppen, J. and Lettice, F., 2016. Management Challenges for DevOps Adoption within UK SMEs. ACM 978-1-4503-4411-1/16/17.
  • Feitelson, D., Frachtenberg, E. and Beck, K. 2013. Development and Deployment at Facebook. IEEE 1089-7801/13
  • Mahanta, P., Adige, V., Pole, A. and Rajkumar, M., 2016. DevOps Culture and its Impact on Cloud Delivery and Software Development. IEEE 978-1-5090-0673-1/16.