6. Conclusions
This case study illustrates the use knowledge management tools in the adoption of DevOps practices by a traditional software vendor as a way of efficiently integrating development, delivery and operations of cloud solutions. DevOps adoption drives a challenging cultural shift towards collaboration and knowledge-sharing between software development, quality control and operations. In this sense, several conclusions can be drawn from this case study. The need for implementing DevOps emerged when Meta4 moved from on premise products to service-oriented cloud solutions. It was a solution to some of the issues regarding cloud solution full functionality.
First, the pressures towards the adoption of DevOps are both internal and external. For instance, technological up to date, availability of technology, reported effectiveness and benefits were identified as the main external pressures. At the same time, DevOps adoption proves able to improve cycle times and quality. However, respondents suggest that although effects at a company level are limited, micro-service architecture could extend the benefits of DevOps beyond the technical side.