Last Updated Oct 01, 2012 — DevOps Expert

During a recent conversation with a leading Forrester analyst four interesting points and predictions came up:

  • DevOps will become NoOps1
  • Model-based automation is required for NoOps
  • The Definitional Model drives the Process Model
  • Scripting and “scripting with a pretty face” (workflows) will decline

The Definitional Model describes the “goal state” of your deployment, i.e. what needs to happen, and the Process Model indicates how that should happen.
At XebiaLabs we’re also strong proponents of model-based automation driven by a Definitional Model (the “Unified Deployment Model” in XL Deploy terms). We want to provide our users with a solution that meets immediate challenges and can also support future developments such as NoOps.What are you seeing in your organization?


  1. You’ll also hear the term AutoOps in places – terminology is still maturing here.

Are you ready to scale your enterprise?


What's New In The World of

August 4, 2023

Why Financial Services Need DevSecOps More Than Ever

With DevSecOps solutions, financial organizations can improve their security posture, meet regulatory requirements and focus on delivering innovative financial products.

Learn More
June 23, 2023

Governance and Compliance for DevOps at Scale

Implement a Software Chain of Custody in DevOps for compliance, traceability, and cost reduction. Gain visibility and automate processes with Release & Deploy.

Learn More
April 10, 2023

Continuous Delivery Implementation Done Right: Learn from National Broadband Ireland Story

Through NBI’s approach to be the best open-access operator in telecom, they have been supported by key technology partners, with automation capabilities provided by Release and Deploy underpinning integral aspects.

Learn More