DevOps can be a distributed set of practices, or be collected into a role. “DevOps” is a software development method that emphasizes communication, collaboration (information sharing and web service usage), integration, automation, and measurement of cooperation between software developers and other IT professionals. The method acknowledges the interdependence of software development, quality assurance, and IT operations, and aims to help an organization rapidly produce software products and services and to improve operations performance.

If DevOps is implemented as a role, these issues will be overseen as a related set of concerns, with a focus that manages their interrelationships. Some of these interrelationships include:

• Have Ops have a kanban board to create visibility on their current workload and therefore expected delays
• Include Ops in the initiation of all work so they know it is coming
• Have all work being done by development that requires Ops indicate that in the MBIs, Features and stories as appropriate.

Resources related to DevOps

Are We Using Automated Acceptance Tests? (Article)
Example RACI Chart for Lean-Agile Roles (Article)
How Is Integration Across Teams Being Handled? (Article)
How Will DevOps Be Involved? (Article)
How Will Shared Services Be Handled? (Article)
Overview of Roles (Article)
To What Extent Will We Automate Tests? (Article)
What Roles Are Missing? Which Roles Need To Be Redefined? (Article)