The expectation of regular software updates – it's what developers are tasked with, and what users expect and demand. Increased functionality, better performance, and fewer bugs – often in a week or less. Automation of critical processes such as QA can help meet the gargantuan task of constant updates, but it can also send your software into a death spiral of user abandonment unless deployed correctly ...
It’s no secret that DevOps is taking the enterprise by storm. In a recent RightScale survey, more than 80 percent of the enterprise and 70 percent of SMBs are adopting DevOps.
At its core, DevOps is about building and delivering quality software at scale. But exactly how you go about doing that is going to vary from company to person to project. DevOps does not look the same anywhere.
As our VP of Worldwide Transformation Justin Arbuckle describes in Data Economy, an effective approach to changing your development processes and teams should start with ALDO – Agile Lean DevOps Outcomes. As he notes, begin with “a practical discussion about what you’re trying to achieve. Then you consider what combination of approaches will help deliver the results you need.” Let’s take a closer look at ALDO:
■ Agile makes and delivers projects in smaller chunks. And the ability to change what you’re building, based on customer feedback, while you’re building it.
■ Lean removes barriers that add friction to your development process. Or those that add friction to your attempts to create value for the customer.
■ DevOps ensures everybody across your organization who is a stakeholder in the outcome of a particular application, is also stakeholder in its creation.
■ Outcome: Now what task in the world isn’t better tackled by breaking it down into smaller pieces? Or adapting if the task changes? Or using more efficient processes? Or collaborating more?
And while these concepts may seem daunting, you don’t need to boil the ocean to get started. As our CEO Barry Crist told Caroline Donnelly of Computerweekly: "The best way to drive change is, instead of having a very conceptual conversation about things, to get people from across the whole IT stack and get them working on one thing. The result will become readily apparent."
So if you’re looking to start driving change inside your organization, it just takes one project and the courage to test out a new approach.
Lucas Welch is Director of Communications at Chef