continuous delivery

Release management is still critical in a DevOps environment. You likely will just have to change your current process. You will no longer need to track implementation or back-out plans as part of change orders; you just need to be able to track the application, its components, and its promotion schedule. The key to maintaining these change orders is automation.

Test coverage is a strategy to help us spend scarce testing time on the right priorities. When things were tested last, how much automation coverage we have, how often the customers use the feature, and how critical the feature is to application are all factors to consider. Here are some ideas for keeping quality high when you're transitioning to continuous delivery.

The core idea of DevOps is the various roles working together to create a stable software system. People can hear that, or read about it, or even observe it, but often, the best way for a team new to DevOps to understand it is to just do it. When you're starting out, that can lead to failures on a real system, so a simulation is a good idea. Try playing a game to introduce your team to DevOps.

Status accounting is following the evolution of a configuration item through its lifecycle. Using application lifecycle management along with agile helps prevent mistakes, but lets you have the minimum amount of red tape; the team achieves an acceptable velocity without being unduly burdened with too much process.