![](bgb.png)
Farcic, V. (2019). DevOps paradox: The truth about De-
vOps by the people on the front line. Packt Publishing,
Birmingham, UK.
Farshchi, M., Schneider, J., Weber, I., and Grundy, J.
(2018). Metric selection and anomaly detection for
cloud operations using log and metric correlation
analysis. Journal of Systems and Software, pages 531–
549.
Fenton, N. and Bieman, J. (2014). Software metrics: a rig-
orous and practical approach. CRC press.
Forsgren, N. (2015). State of DevOps report 2015.
Forsgren, N., Gene, K., Nigel, K., and Jez, H. (2014). State
of DevOps report 2014.
Forsgren, N., Gene, K., Nigel, K., Jez, H., and Brown, A.
(2017). State of DevOps report 2017.
Forsgren, N., Humble, J., and Kim, G. (2018). Accelerate:
State of DevOps report 2018.
Forsgren, N., Smith, D., Humble, J., and Frazelle, J. (2019).
Accelerate: State of DevOps report 2019.
Fowler, M. and Foemmel, M. (2006). Continuous integra-
tion.
Gruver, G. (2016). Starting and scaling DevOps in the en-
terprise. Gary Gruver, [United States].
Gruver, G. (2019). Engineering the Digital Transformation.
Gruver, 1 edition.
Gruver, G., Mouser, T., and Kim, G. (2015). Leading the
transformation: Applying Agile and DevOps princi-
ples at Scale. IT Revolution, Portland, OR.
Harrison, D., Lively, K., and Wang, A. (2019). Achieving
DevOps: A novel about delivering the best of Agile,
DevOps, and microservices. Apress, New York, NY.
Hevner, A. R., March, S. T., Park, J., and Ram, S. (2004).
Design science in information systems research. MIS
quarterly, pages 75–105.
Humble, J. and Farley, D. (2011). Continuous delivery: Re-
liable software releases through build, test, and de-
ployment automation. Addison-Wesley, Upper Saddle
River, NJ.
Kim, G., Humble, J., Debois, P., and Willis, J. (2016).
The DevOps Handbook: How to Create World-Class
Agility, Reliability, and Security in Technology Orga-
nizations. IT Revolution.
K
¨
onig, L. and Steffens, A. (2018). Towards a quality model
for DevOps. Continuous Software Engineering &
Full-scale Software Engineering, page 37.
Lasrado, L., Vatrapu, R., and Andersen, K. (2015). Matu-
rity models development in IS research: A literature
review. volume 6. Scandinavian Chapter of the Asso-
ciation for Information Systems (AIS) - Scandinavian
IRIS. 38th Information Systems Research Seminar in
Scandinavia, IRIS38 ; Conference date: 09-08-2015
Through 12-08-2015.
Likert, R. (1932). A technique for the measurement of atti-
tudes. Archives of psychology.
Linda and ling Lai, S. (2012). Managing user expectations
in information systems development. International
Journal of Economics and Management Engineering,
6(12):3710 – 3714.
Mettler, T. (2011). Maturity assessment models: a design
science research approach. International Journal of
Society Systems Science (IJSSS), 3(1/2):81–98.
Morales-Ramirez, I., Perini, A., and Guizzardi, R. (2015).
An ontology of online user feedback in software engi-
neering. Applied Ontology, 10:297–330.
Object Management Group (2017). Unified Mod-
eling Language (UML), Superstructure, Version
2.5.1. https://www.omg.org/spec/UML/2.5.1 [July 31,
2019].
Peffers, K., Tuunanen, T., Rothenberger, M. A., and Chat-
terjee, S. (2007). A design science research method-
ology for information systems research. Journal of
management information systems, 24(3):45–77.
Poeppelbuss, J., Niehaves, B., Simons, A., and Becker,
J. (2011). Maturity models in information systems
research: literature search and analysis. Communi-
cations of the Association for Information Systems,
29(1):27.
Radstaak, J. (2019). Developing a DevOps maturity model:
A validated model to evaluate the maturity of De-
vOps in organizations. Master’s thesis, University of
Twente.
Rafferty, A. E. and Griffin, M. A. (2004). Dimensions of
transformational leadership: Conceptual and empiri-
cal extensions. The Leadership Quarterly, 15(3):329–
354.
Sharma, S. (2017). The DevOps adoption playbook: A
guide to adopting DevOps in a multi-speed IT enter-
prise. Wiley, Indianapolis IN.
Skelton, M. and Pais, M. (2019). Team topologies: Orga-
nizing business and technology teams for fast flow. IT
Revolution, Portland, Oregon.
Smeds, J., Nybom, K., and Porres, I. (2015). Devops: a def-
inition and perceived adoption impediments. In Inter-
national Conference on Agile Software Development,
pages 166–177. Springer.
Solinski, A. and Petersen, K. (2016). Prioritizing agile ben-
efits and limitations in relation to practice usage. Soft-
ware Quality Journal, 24(2):447–482.
van Hillegersberg, J. (2019). The need for a maturity
model for maturity modeling. In The Art of Structur-
ing, pages 145–151. Springer International Publish-
ing, Cham.
van Ommeren, E., van Doorn, M., Dial, J., and van Herpen,
D. (2016). Mastering digital disruption with DevOps:
Design to disrupt.
von Wangenheim, C. G., Hauck, J. C. R., Salviano, C. F.,
and von Wangenheim, A. (2010). Systematic liter-
ature review of software process capability/maturity
models. In Proceedings of International Conference
on Software Process Improvement and Capabity De-
termination (SPICE), Pisa, Italy.
Wendler, R. (2012). The maturity of maturity model re-
search: A systematic mapping study. Information and
software technology, 54(12):1317–1339.
Westrum, R. (2004). A typology of organizational cultures.
Quality and Safety in Health Care, 13:22–27.
Development of a GQM-based Technique for Assessing DevOps Maturity
127