Weekly Top 10: DevOps’ Transformers and Optimus Equine
Weekly Top 10: DevOps’ Transformers and Optimus Equine
Some of the best recent articles on DevOps and containerization from around the Internet.
Join the DZone community and get the full member experience.Join For Free
Discover how you can reduce your Kubernetes installation from 22 steps to 1.
If this week’s top news showed us anything, it’s all about recognizing the “horses” that are leading DevOps transformations – for these are the journey’s taking place that lead enterprise IT organizations to the land of the high-performers (where the unicorns live). It’s not all blue skies and rainbows along this path however, as history has shown that transforming large and complex organizations not only takes a coalition amongst all the stakeholders, but a significant amount of trust and tactical execution. Don’t be dispelled by the “software delivery” myths or think the journey too long and arduous – believe in the processes you establish and learn/adapt every step of the way! Read on for tips, stories and discussions from industry experts around DevOps maturity and what to be wary of on your journey.
1) As DevOps Matures, IT Ops Evolve Into an IT Service Provider
Embracing DevOps doesn’t mean handing over operations completely to developers — IT ops specialists still have key roles to play. Industry veterans agree IT operations must identify and embrace new ways to add value by becoming internal IT service providers, working in a consultative role with developers, or risk becoming irrelevant.
2) Digital Transformation Strains Traditional IT
As IT leadership had to do in every other transformative period (and cloud, mobile, data analytics are all transformative) such as the displacement of mainframes by PCs in the 1980s, the rise of the local area network and the arrival of the commercial web in the 1990s, IT is at the center of business strategy. CIOs and IT leadership need to make sure they get themselves out in front of these trends and align the services technologies they are delivering with what their users need.
3) Electric Cloud Addresses Scaling Issues with Latest Version of ElectricFlow
Scaling out DevOps initiatives is the next big challenge, according to release automation vendor Electric Cloud. This morning, the company released a new version of its ElectricFlow release automation product. In the announcement, Electric Cloud CEO Steve Brodie indicated that industry discussion about DevOps has shifted from how to get started to how to scale initiatives while also addressing security, compliance, and governance.
4) The Benefits of Using Agile Software Development
Scrum is a flexible and collaborative way to manage a software project. It’s a framework that lets you move quickly and pivot easily when needed. While scrum is favored among many technology leaders, what makes it so attractive for managing projects? Below, technology executives from Forbes Technology Council explain how and why adopting agile methods can help your team achieve their goals.
5) Agile Approaches to DevOps/CD Adoption
Anders Wallgren is the CTO at Electric Cloud. In this episode he shares his thoughts on DevOps lessons from large enterprises, the growth of microservices and containers, and more.
6) How DevOps Can Fix Federal Government IT
There are two words that seem to never go well with each other, bureaucracy and DevOps. Actually, they’re almost complete opposites- bureaucracy is inherently slow and difficult to make significant change within, while DevOps is everything but! Smaller, newer companies are able to implement DevOps practices more easily because they are nimble, and the decision making power lies with small groups or even individuals.
7) Avoiding the ‘Sorcerer’s Apprentice’ Problem of Software Releases
One of my favorite scenes from Disney’s film Fantasia is that of the ‘Sorcerer’s Apprentice’ (originally, a poem by Goethe). Mickey Mouse, as the apprentice, is being trampled by an army of enchanted, cloned brooms. The brooms multiply automatically in an endless march to get the job done, fetching water in buckets to fill up the room and threatening to drown Mickey in the process. For release managers responsible for software delivery in large organisations, managing the multitude of software releases can feel a lot like drowning or being trampled by an army of brooms.
8) DevOps Enters the Mainstream: Here’s How to Make it Work for You
DevOps is a much-hyped methodology that focuses on cooperation and collaboration between software developers and other more operationally-focused IT professionals. It is closely related to the iterative and efficient techniques used in agile and lean methodologies. DevOps should help IT departments create continually evolving services that closely match business demands: analyst Gartner predicts that 2016 is the year when DevOps will become a mainstream approach used by one in four global organisations.
9) 6 Traits Engineers Need to Succeed as IT Leaders
Engineers and developers often make the best IT leaders. Not only are they forward-thinking and tech-savvy, but they’ve already have the trust and the loyalty of your IT team and they know the ins-and-outs of a great culture. If you’re looking for good IT leadership, you should start from within your own ranks, says Kathy Harris, managing director of technology executive recruitment firm Harris Allied. Not only will this foster greater trust and engagement, it can be a powerful recruiting tool for other elite talent, Harris says.
10) 4 Myths About Containers and Continuous Delivery—It Doesn’t get Easier
Developers and technology leaders share a growing misconception that containers can somehow automagically create and turbocharge a continuous delivery pipeline. The contention seems to be that containers enable new features to be rolled out and integrated quickly, providing a predictable and reusable environment, supporting fast feedback, and therefore enabling continuous delivery.
Published at DZone with permission of Anders Wallgren , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.