Getting key stakeholder buy-in for changes perceived as risky
DevOps
Organizational leaders must recognize that change is vital for the sur ...
Read MoreThis post is from the XebiaLabs blog and has not been updated since the original publish date.
As you scale to create an enterprise DevOps process that works effectively across hundreds of applications and thousands of people, you’ll inevitably discover that things don’t work the same way they did back on the developer’s laptop with a single team, or a single environment…
Is your organization kicking off its DevOps transformation? Aiming for wild success? No doubt you’re headed for all sorts of adventures! If you’re like many organizations, you’re setting off on the first full-blown leg of your DevOps journey and your crew’s excitement is palpable. You’ve had a successful DevOps pilot with a team or two, and now it’s time to reach for the stars. Now you’re going to implement DevOps across your enterprise… and if you’re like many intrepid explorers who have gone before you, you have to plan for hundreds or even thousands of people, hundreds or thousands of applications, and thousands of deployments per month. And like those previous pioneers, you’ve probably written a lot of scripts to make your pilot projects work—scripts that create infrastructure, scripts that manage deployments, maybe even scripts that try to orchestrate release pipelines or string together your DevOps toolchain. But as you stretch to implement DevOps at enterprise scale, scripting DevOps can start to consume your teams completely, sucking them into black holes of perpetual maintenance and unmanageability, never to be seen or heard from again. Or at least never to reach the efficiency and productivity your business demands. As you embark on your enterprise DevOps journey, you’ll find you have many new complexities to consider. Here are 11 core DevOps requirements that turn into black holes when you try to write scripts to meet these needs: