Allowing your DevOps teams to develop their own specific mission

Forming a DevOps team for short period of time during a project

Identifying, fixing and learning from errors only after your project ended

Writing code for software to have built-in quality as a main goal

As an audit log that enables the monitoring of all changes

As an optimal way to link development and testing together

To accelerate the delivery of changes to Production

To always maintain the system in a working condition

It allows Development to take over Operations tasks if they have too much work

It allows Operations to automate configuration management using scripts

It allows Operations to be involved in earlier stages of the development

It allows Operations to respond to incidents more quickly than without

Measured service

Percentage complete

Process time

Server time

Because doing so will disrupt the current product and service timelines

Because doing so will increase the number of incidents that occur temporarily

Because it is difficult to deliberately introduce chaos into the Production environment

Because of the high risks of business disruption when integrating large numbers of systems

How long the task has waited

How much the team likes the task

How much value the task adds

How much work the task takes

The boundary between Development and marketing

The boundary between IT management and the rest of the IT department

The boundary between the finance department and Development

The boundary between the HR department and Operations

The boundary between the IT department and the business

Because DevOps extends the agile ideas from IT production to the entire organization, all processes and
the entire value chain

Because DevOps is better than other methodologies for developing software by incorporating
continuous integration and continuous deployment

Because there is no limit to the improvements you can establish with DevOps, due to the continuous
improvement requirement