Framework Proposal for DevOps Maturity Evaluation
Keywords:DevOps; Continuous Delivery; Deployment Pipeline; Continuous Integration; Infrastructure as Code.
This paper proposes a framework for evaluating the DevOps maturity in organizations. The methodology was based on a literature review from which a theory was developed that sought to relate the main DevOps practices. For each of them, some research constructs were defined, which are precisely the objects to be measured by this model. Through a structure based on questions with graded answers, it is possible to indicate how much the unit of analysis that is being evaluated adheres to a DevOps approach in the development and implementation of applications. Therefore, the main contribution of this work is the DevOps maturity evaluation framework that can be easily replicated and, because of that, may be used by several companies to map possible improvement points in their implementation of the DevOps perspective for software development.
AUTOMIC. DevOps Maturity Assessment. Disponível em: <https://automic.com/devops-maturity-assessment>. Acesso em: 5 nov. 2017.
AZOFF, Michael. Ovum Decision Matrix: Selecting a DevOps Release Management Solution, 2016–17. Ovum Software Solutions, mar. 2016. Disponível em: <https://www-01.ibm.com/marketing/iwm/dre/signup?source=ibm-cloud-weborganic&S_PKG=ov47603&dynform=22003>. Acesso em: 5nov. 2017.
BRAGA, Filipe. Um Panorama sobre o uso de Práticas DevOps nas Indústrias de Software. 2015. 123 f. Dissertação (Mestrado)—Curso de Pós-graduação em Ciência da Computação, Centro de Informática da UFPE, Universidade Federal de Pernambuco, Recife, 2015. Disponível em: <http://repositorio.ufpe.br/handle/123456789/15989>. Acesso em: 5nov. 2017.
DUVALL, Paul; MATIAS, Stephen; GLOVER, Andrew. Continuous Integration: improving software quality and reducing risk. New Jersey: Addison-Wesley, 2007.
ERICH, Floris; AMRIT, Chintan; DANEVA, Maya. Report: DevOps Literature Review. University of Twente, out. 2014. Disponível em: <https://www.researchgate.net/profile/Chintan_Amrit/publication/267330992_Report_DevOps_Literature_Review/links/544ba33f0cf2bcc9b1d6bd8a.pdf>. Acesso em: 5 nov. 2017.
FARROHA, Bassam; FARROHA, Debora. A Framework for Managing Mission Needs, Compliance and Trust in the DevOps Environment. IEEE Military Communications Conference, p. 288–293, out. 2014. Disponível em: <http://ieeexplore.ieee.org/document/6956773/references>. Acesso em: 5 nov. 2017.
FEITELSON, Dror; FRACHTENBERG, Eitan; BECK, Kent. Development and Deployment at Facebook. IEEE Internet Computing, v. 17, n. 4, p. 8–17, jul. 2013. Disponível em: <http://ieeexplore.ieee.org/abstract/document/6449236/>. Acesso em: 5nov. 2017.
FRANÇA, Breno de; JERÔNIMO JUNIOR, Hélvio; TRAVASSOS, Guilherme. Characterizing DevOps by Hearing Multiple Voices. Procedings of the 30th Brazilian Symposium on Software Engineering, p. 53–62, set. 2016. Disponível em: <http://dl.acm.org/citation.cfm?id=2973845>. Acesso em: 5 nov. 2017.
GOTTESHEIM, Wolfgang. Challenges, Benefits and Best Practices of Performance Focused DevOps. Proceedings of the 4th International Workshop on Large-Scale Testing, p. 3, fev. 2015. Disponível em: <http://dl.acm.org/citation.cfm?id=2693187>. Acesso em: 5 nov. 2017.
HAMUNEN, Joonas. Challenges in Adopting a Devops Approach to Software Development and Opertions. 2016. 69 f. Dissertação (Mestrado)—MSc program in Information and Service Management, Aalto University, Helsinki, 2016. Disponível em: <https://aaltodoc.aalto.fi/handle/123456789/20766>. Acesso em: 5nov. 2017.
HERNANTES, Josune; GALLARDO, Gorka; SERRANO, Nicolás. IT Infrastructure- Monitoring Tools. IEEE Software, v. 32, n. 4, p. 88–93, ago. 2015. Disponível em: <https://www.computer.org/csdl/mags/so/2015/04/mso2015040088.pdf>. Acesso em: 5 nov. 2017.
HUMBLE, Jez; FARLEY, David. Continuous Delivery: reliable software releases through build, test and deployment automation. New Jersey: Addison-Wesley, 2010.
HUMBLE, Jez; MOLESKY, Joanne. Why enterprises must adopt DevOps to enable continuous delivery. Cutter IT Journal, v. 24, n. 8, p. 6–12, ago. 2011. Disponível em: <https://www.cutter.com/sites/default/files/itjournal/fulltext/2011/08/itj1108.pdf>. Acesso em: 5 nov. 2017.
HÜTTERMANN, Michael. DevOps for developers: integrate development and operations, the agile way. New York: Apress, 2012.
IBM. IBM DevOps Practices Self-assessment. Disponível em: <https://www-01.ibm.com/marketing/iwm/iwm/web/signup.do?source=swg-rtl-sd-calc&S_PKG=ov24988>. Acesso em: 5nov. 2017.
INCYCLE. Online DevOps Assessment. Disponível em: <http://incyclesoftware.com/devops-assessment/>. Acesso em: 5 nov. 2017.
JABBARI, Ramtin et al. What is DevOps? A systematic mapping study on definitions and practices. ACM Digital Library, maio 2016. Disponível em: <http://dl.acm.org/citation.cfm?id=2962707>. Acesso em: 5 nov. 2017.
LIU, Yuhong; LI, Chengbo; LIU, Wei. Integrated Solution for Timely Delivery of Customer Change Requests: a case study of using DevOps approach. International Journal of u- and e- Service, Science and Technology, v. 7, n. 2, p. 41–50, abr. 2014. Disponível em: <http://www.sersc.org/journals/IJUNESST/vol7_no2/4.pdf>. Acesso em: 5 nov. 2017.
MCCARTHY, Matthew et al. Composable DevOps: automated ontology based DevOps maturity analysis. IEEE International Conference on Services Computing, p. 600–607, jun. 2015. Disponível em: <http://ieeexplore.ieee.org/document/7207405/>. Acesso em: 5nov. 2017.
MICROSOFT. DevOps Self Assessment: moving you to the second decade of agile. Disponível em: <https://devopsassessment.azurewebsites.net/>. Acesso em: 5nov. 2017.
PARÉ, Guy et al. Synthesizing information systems knowledge: A typology of literature reviews. Information & Management,v. 52, n. 2, p. 183–199, mar. 2015. Disponível em: <http://www.sciencedirect.com/science/article/pii/S0378720614001116>. Acesso em: 5 nov. 2017.
PENNERS, Ralf; DYCK, Andrej. Release engineering vs. DevOps: an approach to define both terms. Full-scale Software Engineering, fev. 2015. Disponível em: <https://www2.swc.rwth-aachen.de/docs/teaching/seminar2015/FsSE2015papers.pdf#page=53>. Acesso em: 5 nov. 2017.
SHARMA, Sanjeev; COYNE, Bernie. DevOps for dummies. 2. ed. New Jersey: John Wiley & Sons, 2015.
SKELTON, Matthew. Joined-Up Thinking. Oxford Academic ITNow, v. 58, n. 1, p. 40–41, fev. 2016. Disponível em: <https://academic.oup.com/itnow/article-abstract/58/1/40/2392008/Joined-Up-Thinking>. Acesso em: 5nov. 2017.
SPAFFORD, George; HAIGHT, Cameron. Apply Gartner research for a DevOps perspective when implementing a bimodal strategy. Gartner, out. 2014. Disponível em: <https://www.gartner.com/doc/2893418/apply-gartner-research-devops-perspective>. Acesso em: 5 nov. 2017
SPINELLIS, Diomidis. Don’t Install Software by Hand. IEEE Software, v. 29, n. 4, p. 86–87, ago. 2012. Disponível em: <http://ieeexplore.ieee.org/document/6265084>. Acesso em: 5 nov. 2017.
VIRMANI, Manish. Understanding DevOps & bridging the gap from continuous integration to continuous delivery. In:INTERNATIONAL CONFERENCE ON INNOVATIVE COMPUTING TECHNOLOGY, 5., p. 78–82, maio 2015. Disponível em: <http://ieeexplore.ieee.org/abstract/document/7173368/>. Acesso em: 5nov. 2017.
XEBIALABS. DevOps Maturity Quiz. Disponível em: <https://xebialabs.com/devops-maturity-quiz>. Acesso em: 5 nov. 2017.
How to Cite
Authors who publish with this journal agree to the following terms:
1) Authors retain copyright and grant the journal right of first publication with the work simultaneously licensed under a Creative Commons Attribution License that allows others to share the work with an acknowledgement of the work's authorship and initial publication in this journal.
2) Authors are able to enter into separate, additional contractual arrangements for the non-exclusive distribution of the journal's published version of the work (e.g., post it to an institutional repository or publish it in a book), with an acknowledgement of its initial publication in this journal.
3) Authors are permitted and encouraged to post their work online (e.g., in institutional repositories or on their website) prior to and during the submission process, as it can lead to productive exchanges, as well as earlier and greater citation of published work.