{'fraction_non_alphanumeric': 0.013675213675213675, 'fraction_numerical': 0.0, 'mean_word_length': 5.295698924731183, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
A Research on DevOps Maturity Models

Despite the big number of software process models currently available which have been used and practiced for many years, we could not till now totally solve the problem of projects’ late submissions! Meanwhile Software have constantly become bigger, more complex, and require high quality. A recently developed model, called DevOps, aims at producing fast and high-quality releases by bringing the development and operation team to work together. Unfortunately, DevOps is still lacking a clear definition as well as empirical studies that document the experience in implementing and enhancing it. Maturity models are used as a tool to assess the effectiveness of an organizational processes on adopting certain practices and identify what capabilities they need to acquire next in order to improve their performance and reach higher maturity level. However, there are few DevOps maturity models which have been emerged as means to assess DevOps adopted practices. This research aims to identify and benchmark the DevOps maturity models available in literature. We were able to identify several maturity models and compare among them