Highlights from the 2021 State Of DevOps Report

Puppet Inc., founded in 2005 and headquartered in Oregon, Portland, has released its annual DevOps report. This edition is an occasional one, as it marks a decade since the first State of DevOps Report. The report discusses the remote stagnation revolving around the adoption, deployment, and implementation of DevOps practices.

Puppet had come a long way and made a name popularly synonymous with DevOps since its first State of DevOps report a decade ago when DevOps adoption was not as widespread as it is now.

This edition Incorporated 2,657 professionals across IT, information security, and development. 83% of these participants are, to a degree, implementing DevOps practices, with only 18% of these 83% working for highly-evolved organizations. The survey makes us understand that 90% of these highly evolved organizations have automated the most repetitive tasks compared to just 67% got their mid-level counterparts. 91% of the highly-evolved teams displayed clear comprehension of their DevOps responsibilities; these positive reviews would leave readers wondering why the report highlights stagnation in DevOps practices.

Puppet inc. claims the most critical hurdles are more cultural than technical. Suppose DevOps adoption for mid-level organizations is to witness more exponential growth. In that case, there must be a pardon from the currently ubiquitous culture restrictions around an indefinite sense of responsibilities (20%), insufficient feedback loops (17%), slow optimization (18%), risk discouragement (21%).

Another marauding challenge businesses phase is the pressing, unending need to create a state-of-the-art space with a monotonous system of operations to ensure consistent management and security, a system that places constraints on evolution. In a digital conference, Nigel Kersten, a field CTO at Puppet, attested that people are still the biggest barrier to adoption despite more than a decade of DevOps advocacy. Seasoned IT executives base most platform decisions on the cost factor before anything else, leaving less support for development processes. The majority of those platforms are built to be handled by an IT administrator using a graphical tool rather than through command-line interfaces (CLIs) and application programming interfaces (APIs), which DevOps teams prefer.

Increased attention in automation and AI incorporation would spell a better future for DevOps adoption. Nonetheless, it should be evident to concerned personnel that implementing such best practices throughout an entire organization still takes a tremendous amount of time and work and will continue to do so for many years.