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

So that each team member can get their own batch

So that root causes of problems can be identified and resolved quickly

So that the product owner can report back to the customer

So that the product owner has a good idea of what is delivered when

So that there is room for Kaizen blitzes in between work

The team focuses less on the “what” and more on “when”

The team focuses less on the “what and more” on “where”

The team focuses less on the “what” and more on “who”

The team focuses less on the “what” and more on “why”

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

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

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

It increases the team’s responsibility

It improves customer relations

It yields a greater return on IT

Discuss with the Product Owner which work can be shifted to another iteration

Extend the length of this particular iteration to four weeks to remove the bottleneck

Trust that they will solve the bottleneck in the next batch or iteration

The amount of products that are delivered within a timeframe

The sequence of releases that deliver a working product

The series of actions performed to fulfill any type of request

By funding products and not projects, to allow for innovation and optimization

By reassembling a DevOps team for each project to ensure relevant experience

By training the team based on missing knowledge for each new iteration