CI/CD / Cloud Native / DevOps

DevOps Study: How Painful Are Your Deployments and What About All That Stress?

28 Jul 2015 11:09am, by

Want to predict whether an enterprise has a high chance of success? Check if its IT team is implementing continuous delivery and a microservices architecture and you have your answer. Puppet Labs suggests that you only need to ask one question to know how well your IT department is operating: “How painful are deployments?” The answer will not only reveal a business’ IT performance, but their potential business success overall.

To demonstrate the causal link between continuous delivery practices and organizational performance, Puppet Labs published this path diagram based on the survey results of its annual look at the DevOps world:

CD practice path diagram from Puppet Labs

CD practice path diagram from Puppet Labs.

“The more you build quality into the system — through automation, reducing batch sizes and shortening cycle times — and the more effectively you manage your team’s workload and visualize work queues, defects and bottlenecks, the more you increase throughput and stability,” the survey found.

High performing IT teams were deploying code 30 times more frequently than other survey respondents, ending up with production code in effect 200 times faster than their peers. More developers accelerated the frequency of deploying code. As the number of developers in an enterprise rose above 100, an inflection point kicks in where highest performing businesses could successfully increase to three deployments per developer per day.

Surprisingly, there were a myriad of environmental variables that turned out not to be an obstacle to DevOps performance. Things like whether teams use off-the-shelf software, are working on legacy or greenfield projects, or building and integrating on systems of record just didn’t matter that much. The application architecture is the main game for managing performance, it seems.

The other big indicator of success for DevOps is the overall management environment.

Workplace health research has long found that high demand, low control jobs reduce productivity and increase mental health costs such as stress leave and burnout amongst a workforce. “High demand” jobs are jobs that don’t really give workers enough time to do all the tasks expected of them. “Low control” jobs are those where workers are not given the delegative authority to problem solve on their own, have no control of the workplace environment, and who are not provided with the chance to learn new skills.

As is the case in wider industry, so, too, with DevOps: IT performance was higher amongst businesses where developers are given time to learn new skills, are encouraged to understand how their work aligns with overall business goals, are given visual displays of performance metrics, and are encouraged to problem solve.

One of the shortcomings of the survey was the lack of survey response from women. Only 5 percent of the 4,976 survey respondents were women. The authors were surprised by the low participation rate, noting that 13 percent of the systems administration workforce are female. Those responding to the survey, however, were working in predominantly male environments: 33 percent were working on teams with no women and 56 percent were working on teams where less than 10 percent of their colleagues were female.

The authors note that research demonstrates that women in leadership lead to higher financial business performance, with group intelligence higher amongst teams with more women. “Despite all of these clear advantages, organizations are failing to recruit and retain women in technical fields … We can do better. It’s up to all of us to prioritize diversity and promote inclusive environments,” the authors urge.

Featured image: “961120-N-2316H-001” by Expert Infantry is licensed under CC BY 2.0.

Participate in The New Stack surveys and be the first to receive the results of our original research.