From the course: Putting ITIL® into Practice: DevOps for ITIL® Practitioners

Unlock the full course today

Join today to access over 22,700 courses taught by industry experts or purchase this course individually.

Legacy, regulated, and nonautomated environments

Legacy, regulated, and nonautomated environments - ITIL Tutorial

From the course: Putting ITIL® into Practice: DevOps for ITIL® Practitioners

Start my 1-month free trial

Legacy, regulated, and nonautomated environments

“

- [Presenter] At the intersection of DevOps values, and legacy, regulated, and nonautomated environments, focus on the A and the S in CAMS. Automation and sharing. Automation will be constrained by legacy environments that don't lend themselves to automation, or don't make business sense to automate, because release cycles, for example, are infrequent. The obviously thing to do here is to move off legacy environments to the cloud to enable automation where it makes sense to do so. But if that's not possible or business-justified, you can still apply the DevOps value of sharing for tools. Often, tools such as monitoring tools, are not shared across DevonOps and legacy environments for no good reason. This creates an unnecessary divide between DevonOps, especially around nonfunctional requirements, which ITIL calls the warranty aspects of a service. So give some thought to sharing tools to break down that barrier. At the intersection of DevOps principles, the three ways, and legacy…

Contents