Printed on: 28 Jan 2016
Author(s): Robert Hodges (firstname.lastname@example.org) Solution Architecture IBM Systems - Middleware
Co-Author(s) Isabell Sippli, Oliver Kiess, Ingo Boelke, Sacha Mongrain, Bradley Leonard
Sponsor: Ingo Averdunk (email@example.com), Distinguished Engineer, CTO Client Success, IBM Systems - Middleware
The implementation (or transition), to a DevOps development process (the integration of both development,operational teams and processes), has proven itself as an enabler to reducing time to release, improved automation of repetitive processes and a key component of agile development and release. While agile development has led to the increased focus and development of the DevOps model, DevOps is not an all-ornothing change. DevOps can (and should), be introduced and implemented in traditional development environments where appropriate and the improvement can be measured.
However, DevOps is not a single technology, process or tool. While standards are being developed and matured such as SAFe (Scaled Agile Framework), to embrace DevOps requires changes in how teams are structured, how responsibilities are shared and also the need to integrate and deliver services that enables the teams to be successful.
Along with the development solutions and processes, IT Service Management (ITSM) plays a key role in supporting DevOps practices and objectives such as incident management, deployment and application performance management to name but a few.
There are companies (IBM being one), with the portfolio and experience on the concepts, patterns for success and solutions that can assist your journey to DevOps maturity. For the purpose of this document, we are going to limit the discussion to the IT Service Management components and solutions IBM provides that enable or support DevOps integration and automation.
1. Executive Overview
2. Introduction – DevOps & IT Service Management
2.1 Introduction to DevOps
3. Considerations and Motivation (Business Value)
4. Use cases
4.1 Business Needs Require Faster Time-to-Market for Software
4.2 The Capabilities of DevOps are Required, Costs Must be Controlled
4.3 Application Change and Configuration Management
4.4 Application Performance Monitoring
4.5 Business Service Management
4.6 Application Infrastructure Capacity Management
4.7 Application Operation Automation
5. ITSM for DevOps Reference Architecture
5.1 DevOps capabilities and how ITSM can support them
6. Implementation Options
6.1 What or how should you start with ITSM for DevOps?
|ITSM Reference Architecture DevOps Whitepaper|