Introduction to IBM DevOps Practices
BruceMacIsaac 120000D6HD Visits (4075)
This article summarizes why adopting DevOps is critical to fast, lean Enterprise Software Delivery, and describes how the IBM DevOps practices can help you adopt DevOps.
DevOps is an enterprise capability for efficient continuous software delivery. IBM’s approach to DevOps is summarized as follows:
“By applying lean and agile principles across the software delivery lifecycle, DevOps helps organizations deliver a differentiated and engaging customer experience, achieve quicker time to value, and gain increased capacity to innovate.”
The Adoption Framework provides a set of assets that enable the successful adoption of the DevOps capabilities, resulting in measurable business results. It includes 3 key components - Adoption Model, Solutions and Community.
The Adoption Model describes common adoption paths for specific improvement initiatives.
Practitioners can assess where they are, build an adoption roadmap, and collaborate with the DevOps Community. The DevOps Community engages DevOps practitioners to share lessons learned and success stories online. Solutions are like templates – rather than customize a DevOps approach from the ground up, you can start with a pre-configured solution that defines practices, tools, and services for common adoption approaches.
The IBM DevOps Practices are a key component of the IBM’s DevOps Adoption Framework. The practices provide detailed guidance on specific DevOps topic areas and guidance on how to approach DevOps adoption.
What are practices
Every organization follows a set of practices, some documented, some not. Practices define how the organization operates – everything from techniques used for development, to rules and responsibilities for governing who does what and when. Every organizational improvement involves adopting new or changed practices. Thus, adopting DevOps capabilities involves people in the organization adopting DevOps practices.
Training and mentoring are common ways to promote adoption of new and changed practices. However, to know what new practices to adopt, or what practices to change, it helps to have a good description of those practices. A good practice description should include the following:
The DevOps Practices
This initial set of practices will eventually grow to cover other solutions.
The practices website also includes:
The scenario includes how to leverage such assets as the DevOps Lean Assessment, a quick survey to identify areas that need improvement, and the more detailed DevOps Practices Self-Assessment, which uses a practice proficiency model.
The practice proficiency model is composed of specific proficiency levels defined by how well an organization can perform practices, measure outcomes and collaborate. The levels are assessed for each capability and the results are summarized for each adoption path. The assessment looks at consistency, standardization, usage models, defined practices, mentor team or center of excellence, automation, continuous improvement and organizational or technical aspects.
After taking the self-assessments, you can compare your responses to others that have taken the assessments, and you have the option to have a follow-up consultation with a DevOps expert.
Growing the DevOps Practices
The DevOps practices are compatible extensions to the IBM Practices Library (included as part of the Rational Method Composer product), which provide broad coverage of software and systems development methods. The practices can be customized and combined to define complete software and systems development processes, as well as to configure/automate aspects of processes. See the article series Document and automate processes with Rational Method Composer and Jazz.
Our intention is to grow this initial set of practices to cover other areas of DevOps.
If you have comments on these practices, or suggestions on additional areas to cover, please post in the DevOps community forum.
See a brief recorded demo of the DevOps Practices.
Visit the DevOps Practices website: