DevOps For Everyone: Bringing DevOps Success to Every App and Every Role in your Organization

Editor's Notes

• #11: There is no official catalog of DevOps practices. As such, individual organizations must not only define what DevOps is to them, but also identify the activities that come into the DevOps focus. This figure is Gartner's initial attempt at providing some "bounded rationality" to the question: "What does DevOps consist of?“ …organization style attributed to Google, an SRE team = "… combines software development, networking and system engineering expertise to build and run large scale, massively distributed, fault tolerant software systems and infrastructure.“ …organization style modeled after Amazon.com's "two pizza" teams, a Feature team = “….have an integrated team of developers, quality assurance (QA), production engineers, and program or product managers, typically numbering between six and 10 individuals in total” ChatOps —ChatOps is an approach generally credited to GitHub. It is the pattern of automating operations tasks with an automated chat robot, or "bot," from within a chat room. Specifically, DevOps team members issue commands to perform code deployments, for example, via Internet Relay Chat (IRC) to a chat bot, which then executes them through scripts, etc. This enables the entire team to have real time collaboration, and ensures that everyone is aware of the current status of an operation in progress. A DevOps project can start from within any of the four basic areas or paths. It is less important to have a specific starting point than to just start and iterate toward the desired objective. In addition, it is not necessary to fully implement every practice within a category —organizations should stop at the point where they've determined that they've implemented the capabilities necessary for their business.
• #22: Apply a Layered Operations Strategy Reflecting the Reality That Not All IT Services Have the Same Support Requirements. Different applications cause different rates of change versus stability. Gartner’s ‘Pace-Layered Application Strategy’ outlines a way to categorize applications into: 1. Systems of record (typically ERP-type applications) 2. Systems of differentiation (typically business-specific applications, often COTS applications with customization) 3. Systems of innovation (typically new web-based, agile-development-focused applications) Stabilize IT Operations Investment in Systems of Record, and Begin to Shift IT Management Funding to Systems of Innovation and Systems of Differentiation That Will Drive Greatest Incremental Value for the Business DevOps as a concept is well aligned with projects with high degrees of uncertainty, so exhaustive planning is not going to be optimal.
• #27: Measuring Availability / Uptime Measuring the Business Differentiation How quickly we can deploy business differentiation to the market? # of deployments New functionality