You’ve likely heard the buzzword, ‘DevOps’, tossed around — boasting higher quality code, faster time to market, and continuous innovation. But, is DevOps for every team and organization?
As managers and executives, we know that the business environment in which we operate is rarely perfect. Team members are frequently inherited, constant training on the latest module is required, and budgets are often miscalculated. Many of these conditions contribute to delayed launches, subpar user experience, and unhappy business stakeholders. All in all, not a winning combination.
Knowing this, I’m sure you’ve been scouring the industry for the right solution. You’ve likely heard the buzzword, ‘DevOps’, tossed around — boasting higher quality code, faster time to market, and continuous innovation. But, is DevOps for every team and organization? I’m not so sure… In fact, to help you assess the opportunity, I’ve put together 4 compelling reasons why your enterprise shouldn’t invest in DevOps:
1. Good enough is good enough
Some might argue that velocity is the most important yardstick to measure the success of agile software development teams. But, I like to subscribe the philosophy “if it ain’t broke, don’t fix it”. The real-time visibility DevOps offers for pipeline performance and management of multiple, in flight, projects might seem like a value add, but really, transparency and tracking is so overrated. Wouldn’t you agree? I prefer to look at successful project planning, collaboration, and team cohesion as a happy accident – too much transparency ruins the magic!
2. Thinking now is better than thinking big
Visibility into multiple ongoing projects can only lead to confusion. Better than moving multiple priorities forward is putting on the blinders and building something exactly as planned. While the capability to visualize all of your teams’ software pipeline performance exists, thanks to tools like CloudBees Jenkins, won’t all that access just keep you up at night? Better keep it simple and focus on one thing at a time – even if that means falling behind on other deployments and priorities.
3. The first idea is always the best idea
While some might suggest that mid-course correction and the ability to pivot when challenges arise is crucial to good technical leadership, shouldn’t we be focusing on validating the initial technical investment by committing to and executing the original plan? You may have heard the term “technical debt” floating around. This refers to the additional work that arises from taking a code “shortcut” to implement easy to run code instead of the best overall solution. The practice of DevOps reduces technical debt by embracing a shift in
4. The Cloud may be the way of the future, but you’re sure Mainframe is making a comeback.
Yup. Just one more reason that DevOps isn’t for you and your enterprise business.
You’ve likely realized that this article was written as a satire. At