Context: Businesses today need to respond to customer needs at unprecedented speed.Driven by this need for speed, many companies are rushing to the DevOps movement. DevOps, the combination of Development and Operations, is a new way of thinking in the software engineering domain that recently received much attention. Since DevOps has recently been introduced as a new term and novel concept, no common understanding of what it means has yet been achieved. Therefore, the definitions of DevOps often are only a part relevant to the concept. When further observing DevOps, it could be seen as a movement, but is still young and not yet formally defined. Objective: This research intends to develop a maturity model to assist professionals during DevOps implementation. Method: Design Science research was the research methodology used. Plus, two Systematic Literature Reviews were performed. The first to elicit DevOps areas and the second to elicit DevOps practices. Then, 15 experts were interviewed in a first round and 13 in a second round aiming to reach more consensus on the results. Becker guidelines were also followed to develop the maturity model. Results: A maturity model was created grounded on academics and professionals' viewpoints. Th artefact was then demonstrated and evaluated in two organizations. The results point that the proposed maturity model is useful for organizations. Conclusion: Organizations are able to understand their strongest and weakest capabilities/areas and take further actions. A maturity model is an important mechanism for DevOps implementation. The fast growth pace of DevOps adoption worldwide raises attention on this mechanism.

No abstract

This research aims to investigate how DevOps culture can be applied in the incident management process. The authors believe, based on experience as practitioners, that agile software development methodologies are fair enough to be used on Incident Management process, to quickly restore the business interruption. An application management team which solves incidents and applies DevOps practices was studied. Three data collection methods were used: interviews, document analysis and observation. This research provides novel findings supported by metrics and real experience implementing DevOps practices in incident management process. The novelty of the findings brings advantages for academics, and due to the exploratory nature of this research, it extends the body of knowledge. It also provides contributions for practitioners, by showing how these practices can be applied and the result of the implementation of these practices. Directions of future work are also presented.