Evaluación de la madurez DevOps en una organización mediante la aplicación de una técnica basada en GQM
| dc.contributor.advisor | Aponte Melo, Jairo Hernán | |
| dc.contributor.author | Herrera Maldonado, Juan Sebastián | |
| dc.contributor.researchgroup | Ingeniería de Software | |
| dc.coverage.temporal | Colombia | |
| dc.date.accessioned | 2026-02-11T20:02:35Z | |
| dc.date.available | 2026-02-11T20:02:35Z | |
| dc.date.issued | 2025 | |
| dc.description | Ilustraciones | spa |
| dc.description.abstract | El enfoque DevOps se ha consolidado como un pilar estratégico para que las organizaciones puedan desarrollar, probar y desplegar software de forma ágil, frecuente y confiable. Su objetivo primordial es romper las barreras tradicionales entre el desarrollo y las operaciones de TI, facilitando una colaboración integral que se traduzca en una entrega de valor continua y adaptada a las cambiantes demandas del mercado. Como afirman [5], “DevOps representa una convergencia necesaria de las prácticas de desarrollo y operaciones, permitiendo a las organizaciones responder de manera rápida y eficaz a los requerimientos del entorno”. A pesar de los múltiples casos de éxito que demuestran cómo la adopción de DevOps puede optimizar procesos y acelerar la innovación, la transición hacia este modelo no está exenta de retos. Se han documentado numerosas dificultades, especialmente en organizaciones con estructuras jerárquicas y procesos tradicionales arraigados, donde la resistencia al cambio y la falta de una cultura colaborativa constituyen obstáculos significativos. Esta dualidad—entre el potencial transformador y los desafíos de implementación—subraya la necesidad de contar con métodos de evaluación que permitan diagnosticar de forma precisa el nivel de madurez DevOps dentro de una organización. El presente trabajo final aborda esta problemática a través de un estudio de caso en una organización FinTech, evaluando su grado de madurez DevOps mediante la aplicación de una técnica basada en GQM (Goal-Question-Metric). La metodología GQM, ampliamente reconocida por su capacidad para traducir metas estratégicas en preguntas y métricas cuantificables, proporciona un marco estructurado que facilita la toma de decisiones informadas y la identificación de áreas críticas de mejora. [11] destacan que “la técnica GQM ofrece un marco robusto para evaluar el desempeño y orientar la mejora continua, permitiendo una alineación precisa entre los objetivos organizacionales y las prácticas operativas”. El estudio de caso realizado en conjunto con los equipos de la organización reveló que la evaluación basada en GQM logró capturar de manera fidedigna la situación actual de las capacidades y el desempeño en materia de DevOps. Este diagnóstico no solo permitió establecer un punto de referencia claro, sino que también facilitó la elaboración de un plan piloto que priorice el fortalecimiento de aquellos componentes críticos identificados durante el análisis. En este sentido, la implementación de la técnica GQM se configuró como una herramienta clave para la toma de decisiones estratégicas, permitiendo a la organización avanzar hacia una adopción más completa y sostenible de las prácticas DevOps. La integración de DevOps mediante un enfoque evaluativo basado en GQM no solo evidencia la viabilidad y eficacia de este modelo en entornos altamente competitivos y dinámicos, sino que también subraya la importancia de contar con métricas objetivas y un análisis profundo para gestionar la transformación cultural y tecnológica. Este trabajo respalda la premisa de que, a pesar de los desafíos inherentes a la transición, la implementación de DevOps es esencial para alcanzar niveles superiores de agilidad, eficiencia y calidad en la entrega de software, posicionando a la organización FinTech en una trayectoria de innovación y competitividad sostenida. (Texto tomado de la fuente) | spa |
| dc.description.abstract | The DevOps approach has established itself as a strategic pillar for organizations to develop, test, and deploy software in an agile, frequent, and reliable manner. Its primary objective is to break down the traditional barriers between development and IT operations, facilitating comprehensive collaboration that translates into continuous value delivery adapted to changing market demands. As [5] state, “DevOps represents a necessary convergence of development and operations practices, allowing organizations to respond quickly and effectively to environmental requirements.” Despite the many success stories demonstrating how adopting DevOps can optimize processes and accelerate innovation, the transition to this model is not without challenges. Numerous difficulties have been documented, especially in organizations with hierarchical structures and entrenched traditional processes, where resistance to change and a lack of a collaborative culture constitute significant obstacles. This duality— between transformative potential and implementation challenges—underscores the need for assessment methods that accurately diagnose the level of DevOps maturity within an organization. This final thesis addresses this issue through a case study of a FinTech organization, assessing its level of DevOps maturity by applying a technique based on GQM (GoalQuestion-Metric). The GQM methodology, widely recognized for its ability to translate strategic goals into quantifiable questions and metrics, provides a structured framework that facilitates informed decision-making and the identification of critical areas for improvement. [11] emphasize that “the GQM technique offers a robust framework for evaluating performance and guiding continuous improvement, enabling precise alignment between organizational objectives and operational practices.” The case study, conducted jointly with the organization's teams, revealed that the GQMbased assessment accurately captured the current state of DevOps capabilities and performance. This diagnosis not only allowed for the establishment of a clear benchmark but also facilitated the development of a pilot plan that prioritizes the strengthening of the critical components identified during the analysis. In this sense, the implementation of the GQM technique emerged as a key tool for strategic decision-making, allowing the organization to move toward a more comprehensive and sustainable adoption of DevOps practices. The integration of DevOps through a GQM-based evaluative approach not only demonstrates the viability and effectiveness of this model in highly competitive and dynamic environments but also underscores the importance of objective metrics and indepth analysis to manage the cultural and technological transformation. This work supports the premise that, despite the challenges inherent in the transition, the implementation of DevOps is essential to achieving higher levels of agility, efficiency, and quality in software delivery, positioning the FinTech organization on a path of sustained innovation and competitiveness. | eng |
| dc.description.degreelevel | Maestría | |
| dc.description.degreename | Magíster en Ingenería de Sistemas y Computación | |
| dc.description.methods | Para este trabajo final se realizó una investigación de tipo descriptiva con una estrategia de investigación cuantitativa y un diseño no-experimental más puntualmente un diseño transversal, ya que se realizará la recolección de datos en un solo punto del tiempo, involucrando métodos como cuestionarios y entrevistas estructuradas. Para alcanzar los objetivos propuestos se llevará a cabo la siguiente metodología de 3 etapas: Etapa I: Planeación de la evaluación: En esta etapa se realizan todos los preparativos y análisis previos requeridos para la correcta aplicación del assessment en la organización. Etapa II: Aplicación de la evaluación: En esta etapa se implementa la técnica GQM como tal en la organización basándose en los entregables de la etapa I. Etapa III: Determinación del nivel de madurez Esta es la etapa más importante porque en ella se realiza el análisis de los resultados obtenidos y se determina el nivel de madurez de la organización. | spa |
| dc.description.researcharea | Maestría en Ingeniería – Ingeniería de Sistemas y Computación | |
| dc.format.extent | 131 páginas | |
| dc.format.mimetype | application/pdf | |
| dc.identifier.instname | Universidad Nacional de Colombia | spa |
| dc.identifier.reponame | Repositorio Institucional Universidad Nacional de Colombia | spa |
| dc.identifier.repourl | https://repositorio.unal.edu.co/ | spa |
| dc.identifier.uri | https://repositorio.unal.edu.co/handle/unal/89505 | |
| dc.language.iso | spa | |
| dc.publisher | Universidad Nacional de Colombia | |
| dc.publisher.branch | Universidad Nacional de Colombia - Sede Bogotá | |
| dc.publisher.faculty | Facultad de Ingeniería | |
| dc.publisher.place | Bogotá, Colombia | |
| dc.publisher.program | Bogotá - Ingeniería - Maestría en Ingeniería - Ingeniería de Sistemas y Computación | |
| dc.relation.references | Bahrs, P. G. (2013). Adopting the IBM DevOps approach for continuous software delivery: Adoption paths and the DevOps maturity model. IBM Developer. Retrieved from https://developer.ibm.com/articles/d-adoption-paths/ | |
| dc.relation.references | Bang, S. K., Chung, S., Choh, Y., & Dupuis, M. (2013, October). A grounded theory analysis of modern web applications: Knowledge, skills, and abilities for DevOps. En Proceedings of the 2nd Annual Conference on Research in Information Technology (pp. 61–62). ACM. https://doi.org/10.1145/2512209.2512229 | |
| dc.relation.references | Bucena, I., & Kirikova, M. (2017). Simplifying the DevOps Adoption Process. En BIR Workshops (Vol. 1898, pp. 1–15). CEUR-WS. Retrieved from https://ceur-ws.org/Vol-1898/paper14.pdf | |
| dc.relation.references | CA Technologies. (2014). TechInsights Report: What Smart Businesses Know About DevOps. Retrieved from https://www.logicworks.com/wpcontent/uploads/2016/01/techinsights-report-what-smart-businesses-knowaboutdevops.pdf | |
| dc.relation.references | Chef. (2022). Chef Software DevOps Automation Solutions. Retrieved from https://www.chef.io/ | |
| dc.relation.references | Cusumano, M. A., & Selby, R. W. (1998). Microsoft Secrets: How the world’s most powerful software company creates technology, shapes markets, and manages people. Simon & Schuster. Retrieved from https://www.simonandschuster.com/books/Microsoft-Secrets/Michael-ACusumano/9780684836370 | |
| dc.relation.references | Bayser, M., Azevedo, L. G., & Cerqueira, R. (2015). ResearchOps: The case for DevOps in scientific applications. En 2015 IFIP/IEEE International Symposium on Integrated Network Management (IM) (pp. 1398–1404). IEEE. https://doi.org/10.1109/INM.2015.7140503 | |
| dc.relation.references | Debois, P. (2011). DevOps: A software revolution in the making. Journal of Information Technology Management, 24(8), 3–39. Retrieved from https://www.cutter.com/article/devops-software-revolution-making-416511 | |
| dc.relation.references | Díaz, J., López-Fernández, D., Pérez, J., & González-Prieto, Á. (2021). Why are many businesses instilling a DevOps culture into their organization? Empirical Software Engineering, 26(2), 1–50. https://doi.org/10.1007/s10664-020-09919-3 | |
| dc.relation.references | Düllmann, T. F., Paule, C., & van Hoorn, A. (2018). Exploiting DevOps practices for dependable and secure continuous delivery pipelines. In Proceedings of the 4th International Workshop on Rapid Continuous Software Engineering (RCoSE 2018) @ ICSE 2018 (pp. 27–30). ACM. https://doi.org/10.1145/3194760.3194763 | |
| dc.relation.references | Eficode Oy. (2015). DevOps Quick Guides. Helsinki, Finland. Retrieved from https://www.eficode.com/devops-quick-guides | |
| dc.relation.references | Feitelson, D. G., Frachtenberg, E., & Beck, K. L. (2013). Development and deployment at Facebook. IEEE Internet Computing, 17(4), 8–17. https://doi.org/10.1109/MIC.2013.25 | |
| dc.relation.references | Fitzgerald, B., & Stol, K.-J. (2014). Continuous software engineering and beyond: Trends and challenges. In Proceedings of the 1st International Workshop on Rapid Continuous Software Engineering (RCoSE 2014) (pp. 1–9). Association for Computing Machinery. https://doi.org/10.1145/2593812.2593813 | |
| dc.relation.references | França, B. B. N., Jeronimo, H., & Travassos, G. H. (2016). Characterizing DevOps by hearing multiple voices. In Proceedings of the 30th Brazilian Symposium on Software Engineering (SBES ’16) (pp. 53–62). ACM Press. https://doi.org/10.1145/2981775.2981784 | |
| dc.relation.references | Freeman, E. (2019). DevOps For Dummies. John Wiley & Sons. Retrieved from https://www.wiley.com/en-us/DevOps%2BFor%2BDummies-p9781119552222 16) Google. (2021). Explore el programa de investigación de DORA. Google Cloud DevOps Research and Assessment (DORA). Retrieved from https://cloud.google.com/devops#section-1 | |
| dc.relation.references | Hamunen, J., Porras, J., & Systä, T. (2016). Challenges in adopting a DevOps approach to software development and operations. Aalto University. Retrieved from https://aaltodoc.aalto.fi/server/api/core/bitstreams/2d3a6642-0159-4365- 994d-96ed1ba55e81/content | |
| dc.relation.references | Humble, J., & Molesky, J. (2011, August 24). Why enterprises must adopt DevOps to enable continuous delivery. Cutter IT Journal. Retrieved from https://www.cutter.com/article/why-enterprises-must-adopt-devopsenablecontinuous-delivery-416516 | |
| dc.relation.references | Hüttermann, M. (2012). DevOps for Developers: Integrate Development and Operations. Packt Publishing. Retrieved from https://www.amazon.com/DevOpsDevelopers-Experts-Voice-Development/dp/1430245697 | |
| dc.relation.references | Inbar, S., Yaniv, S., Gil, P., Eran, S., Ilan, S., Kogan, O., & Ravi, S. (2013). DevOps and OpsDev: How Maturity Model Works. Hewlett Packard Enterprise. Retrieved from https://community.softwaregrp.com/t5/All-About-theApps/DevOps-and-OpsDev-How-Maturity-Model-Works/ba-p/306787 | |
| dc.relation.references | Jones, D. T., & Womack, J. P. (2012). Lean Thinking (Rev. & updated ed.). Free Press. Retrieved from https://www.amazon.com/Lean-Thinking-CorporationRevised-Updated/dp/0743249275 | |
| dc.relation.references | Khan, A. A., & Shameem, M. (2020). Multicriteria decision-making taxonomy for DevOps challenging factors using analytical hierarchy process. Journal of Software: Evolution and Process, 32. https://doi.org/10.1002/smr.2263 | |
| dc.relation.references | Kim, G. (2013). Top 11 things you need to know about DevOps. Retrieved from http://www.bogotobogo.com/DevOps/Puppet/images/DevOps/Top11ThingsTo K nowAboutDevOps.pdf | |
| dc.relation.references | Kim, G., Behr, K., & Spafford, K. (2014). The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win. IT Revolution. Retrieved from https://itrevolution.com/book/the-phoenix-project/ | |
| dc.relation.references | Laukkarinen, T., Kuusinen, K., & Mikkonen, T. (2018). Regulated software meets DevOps. Information and Software Technology, 97, 176–178. https://doi.org/10.1016/j.infsof.2018.01.010 | |
| dc.relation.references | Luz, W. P., Pinto, G., & Bonifácio, R. (2018). Building a collaborative culture: A grounded theory of well-succeeded DevOps adoption in practice. In Proceedings of the 12th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (pp. 1–10). ACM. https://doi.org/10.1145/3239235.3240282 | |
| dc.relation.references | Lwakatare, L. E., Kuvaja, P., & Oivo, M. (2015). Dimensions of DevOps. In International Conference on Agile Software Development (pp. 212–217). Springer. https://link.springer.com/chapter/10.1007/978-3-319-18526-0_28 | |
| dc.relation.references | Lwakatare, L. E., Kuvaja, P., & Oivo, M. (2016). An exploratory study of DevOps: Extending the dimensions of DevOps with practices. Proceedings of the 11th International Conference on Software Engineering Advances (ICSEA 2016), 2016. Retrieved from https://ieeexplore.ieee.org/document/7892865 | |
| dc.relation.references | Menzel, G., Macaulay, A., Ajith, N. C., & Dhanesh, A. (2015). DevOps – The Future of Application Lifecycle Automation. Capgemini Architecture Whitepaper. Retrieved from https://www.capgemini.com/wpcontent/uploads/2017/07/whitepaper-devopslifecycleautomation.pdf | |
| dc.relation.references | Mohamed, S. I. (2015). DevOps shifting software engineering strategy: A valuebased perspective. IOSR Journal of Computer Engineering, 17(4), 51–57. https://doi.org/10.9790/0661-17245157 | |
| dc.relation.references | Neubrand, T., & Haendler, T. (2020). Development of a GQM-based Technique for Assessing DevOps Maturity. International Journal of Software Engineering and Knowledge Engineering, 30(3), 345–360. Retrieved from https://www.worldscientific.com/doi/10.1142/S0218194020500123 | |
| dc.relation.references | Nielsen, P. A., Winkler, T. J., & Nørbjerg, J. (2017). Closing the IT developmentoperations gap: The DevOps knowledge sharing framework. In BIR Workshops (Vol. 1898, pp. 45–58). CEUR-WS. Retrieved from http://ceur-ws.org/Vol1898/paper08.pdf | |
| dc.relation.references | Poppendieck, M. (2007). Lean software development. In Proceedings of the 29th International Conference on Software Engineering (ICSE’07 Companion) (pp. 165–166). IEEE. https://doi.org/10.1109/ICSE.2007.97 | |
| dc.relation.references | Puppet & DORA. (2016). Annual State of DevOps Report. Puppet. Retrieved from https://puppet.com/resources/report/2016-state-devops-report | |
| dc.relation.references | Puppet & DORA. (2020). Puppet State of DevOps Report 2020. Puppet. Retrieved from https://media.webteam.puppet.com/uploads/2020/11/PuppetState-ofDevOps-Report-2020.pdf | |
| dc.relation.references | Puppet. (2021). Powerful infrastructure automation and delivery. Retrieved from https://puppet.com/ | |
| dc.relation.references | Shamow, E. (2011). DevOps at Advance Internet: How we got in the door. Cutter IT Journal, 14(8), 22–28. Retrieved from https://www.cutter.com/article/devopsadvance-internet-how-we-got-door416519 | |
| dc.relation.references | Sharma, S. (2017). The DevOps Adoption Playbook: A Guide to Adopting DevOps in a Multi-Speed IT Enterprise. John Wiley & Sons. https://www.wiley.com/enus/The+DevOps+Adoption+Playbook%3A+A+Guide+to+ Adopting+DevOps+i n+a+Multi+Speed+IT+Enterprise-p-9781119257862 | |
| dc.relation.references | Sharma, S., & Coyne, B. (2015). DevOps For Dummies (2nd IBM Limited Edition). John Wiley & Sons. Retrieved from https://www.dummies.com/book/technology/programmingwebdesign/devops/devops-for-dummies-2nd-edition-281671/ | |
| dc.relation.references | Soni, M. (2015). End-to-end automation on cloud with build pipeline: The case for DevOps in the insurance industry. In 2015 IEEE International Conference on Cloud Computing in Emerging Markets (CCEM) (pp. 85–89). IEEE. https://doi.org/10.1109/CCEM.2015.17 | |
| dc.relation.references | Sonninen, O. (2020). Perceived benefits of declarative software deployment: An exploratory case study. Lappeenranta–Lahti University of Technology. Retrieved from https://lutpub.lut.fi/bitstream/10024/161089/1/Perceived_Benefits_of_Declarati v e_Software_Deployment_An_Exploratory_Case_Study.pdf | |
| dc.relation.references | Steffens, A., Lichter, H., & Döring, J. S. (2018). Designing a next-generation continuous software delivery system: Concepts and architecture. In Proceedings of the 4th International Workshop on Rapid Continuous Software Engineering (RCoSE ’18) (pp. 1–7). ACM. https://doi.org/10.1145/3194760.3194768 | |
| dc.relation.references | Teixeira, D., Pereira, R., Henriques, T. A., Silva, M., & Faustino, J. (2020). A systematic literature review on DevOps capabilities and areas. International Journal of Human Capital and Information Technology Professionals, 11(2), 1– 22. https://doi.org/10.4018/IJHCITP.2020040101 | |
| dc.relation.references | The Agile Admin. (2011, February 24). What is DevOps? The Agile Admin. Retrieved from https://theagileadmin.com/what-is-devops/ | |
| dc.relation.references | Tuma, K., Calikli, G., & Scandariato, R. (2018). Threat analysis of software systems: A systematic literature review. Journal of Systems and Software, 144, 275–294. https://doi.org/10.1016/j.jss.2018.06.005 | |
| dc.relation.references | van Doorn, J. D. M., & van Herpen, D. (2020). Design to Disrupt. Harvard Business Review Press. Retrieved from https://hbr.org/product/designtodisrupt/10141-PBK-ENG | |
| dc.relation.references | van Hillegersberg, J. (2019). The need for a maturity model for maturity modeling. In The Art of Structuring (pp. 145–151). Springer. https://link.springer.com/chapter/10.1007/978-3-030-06234-7_14 | |
| dc.relation.references | Willis, J. (2017). DevOps in a Serverless World. Retrieved from https://www.youtube.com/watch?v=Iw88FWfhk_I | |
| dc.relation.references | Womack, J. P., Jones, D. T., & Roos, D. (2007). The machine that changed the world: The story of lean production—Toyota’s secret weapon in the global car wars that is now revolutionizing world industry (Rev. ed.). Free Press. Retrieved from https://www.simonandschuster.com/books/The-Machine-That-ChangedtheWorld/James-P-Womack/9780743297584 | |
| dc.relation.references | Zarour, M., Alhammad, N., Alenezi, M., & Alsarayrah, K. (2019). A research on DevOps maturity models. International Journal of Recent Technology and Engineering, 8(3), 4854–4862. https://doi.org/10.35940/ijrte.C6888.098319 | |
| dc.rights.accessrights | info:eu-repo/semantics/openAccess | |
| dc.rights.license | Atribución-NoComercial-SinDerivadas 4.0 Internacional | |
| dc.rights.uri | http://creativecommons.org/licenses/by-nc-nd/4.0/ | |
| dc.subject.armarc | Desarrollo ágil de software | spa |
| dc.subject.bne | Métrica del software | spa |
| dc.subject.bne | Software -- Evaluación | spa |
| dc.subject.bne | Software -- Control de calidad | spa |
| dc.subject.ddc | 620 - Ingeniería y operaciones afines | |
| dc.subject.lcc | Agile software development | eng |
| dc.subject.lcc | Software measurement | eng |
| dc.subject.lcc | Computer software -- Quality control | eng |
| dc.subject.proposal | Evaluación | spa |
| dc.subject.proposal | Modelo de Madurez | spa |
| dc.subject.proposal | Adopción de DevOps | spa |
| dc.subject.proposal | Automatización | spa |
| dc.subject.proposal | Servidor de Entrega Continua | spa |
| dc.subject.proposal | GQM | spa |
| dc.subject.proposal | Maturity Model | eng |
| dc.subject.proposal | DevOps Adoption | eng |
| dc.subject.proposal | Automation | eng |
| dc.subject.proposal | Continuous Delivery Server | eng |
| dc.title | Evaluación de la madurez DevOps en una organización mediante la aplicación de una técnica basada en GQM | spa |
| dc.title.translated | DevOps Maturity Evaluation In An Organization Through The Application Of A Technique Based On GQM | eng |
| dc.type | Trabajo de grado - Maestría | |
| dc.type.coar | http://purl.org/coar/resource_type/c_bdcc | |
| dc.type.coarversion | http://purl.org/coar/version/c_ab4af688f83e57aa | |
| dc.type.content | Text | |
| dc.type.driver | info:eu-repo/semantics/masterThesis | |
| dc.type.redcol | http://purl.org/redcol/resource_type/TM | |
| dc.type.version | info:eu-repo/semantics/acceptedVersion | |
| dcterms.audience.professionaldevelopment | Público general | |
| dcterms.audience.professionaldevelopment | Estudiantes | |
| dcterms.audience.professionaldevelopment | Maestros | |
| dcterms.audience.professionaldevelopment | Público general | |
| dcterms.audience.professionaldevelopment | Especializada | |
| oaire.accessrights | http://purl.org/coar/access_right/c_abf2 |
Archivos
Bloque original
1 - 1 de 1
Cargando...
- Nombre:
- DocumentoFinal1031167991.pdf
- Tamaño:
- 2.67 MB
- Formato:
- Adobe Portable Document Format
- Descripción:
- Tesis de la Maestría en Ingeniería – Ingeniería de Sistemas y Computación
Bloque de licencias
1 - 1 de 1
Cargando...
- Nombre:
- license.txt
- Tamaño:
- 5.74 KB
- Formato:
- Item-specific license agreed upon to submission
- Descripción:

