Accelerating software innovation
DevOps represents the better fusion of the commonly distinct functions of IT Operations and Software Development, to accelerate product and software innovation rates.
This Enterprise DevOps section provides a complete implementation reference model and framework for large enterprise organizations.
TRANSFORM Blueprints offer a complete business transformation toolkit, tailored to enable implementation of Enterprise DevOps through a best practice process:
- Define your DevOps ROI & KPIs Scorecard - What specific performance improvements would you like to achieve? What are the business benefits? How well are these being achieved?
- Capability Application Mapping - Transposing target architecture business models on to new Cloud service configurations.
- Implementation Recipes - Methods of implementing these configurations including vendor profiles and supplier options.
Fundamentally achieved through the following transformation journeys:
- 'From Siloes to DevOps' through Implementing Business Capability Teams
- From Monolith to Microservices
Resources to help plan these journeys:
TRANSFORM Business Benefits
Research from the IT Process Institute benchmarked over 1,500 IT organizations and concluded that high-performing IT organizations utilizing DevOps were on average:[/su_service]
5-7x times more productive than their non-high performing peers.
They were making 14x more changes, with one-half the change failure rate with 4x higher first fix rates, and 10x shorter Severity 1 outages times.
They had 4x fewer repeat audit findings, they were 5x more likely to detect breaches by an automated internal control, and had 8x better project due date performance!
In particular the aspect of shifting to a Continuous Delivery approach is key, the much faster software development and deployment cycles that DevOps focuses on, to achieve the higher throughput rates with fewer code failures.
A discussion about how REAN Cloud partnered with their customer, Ellucian, to develop DevOps framework to transform their software delivery process for over 80 product lines.
Attendees walked away with a thorough understanding of a real-world continuous integration/ continuous delivery framework leveraging Packer, Jenkins, Vagrant, Terraform, along with best practices and overcoming of challenges.
This approach to defining an Enterprise DevOps Scorecard reflects both an overall business case agenda as well as practical enhancements for software and operations teams.
The fundamental goal is one of 'Increasing Business Value Throughput', the rates at which IT can convert opportunites and requirements into $ revenue generating client services and solutions.
Defining DevOps KPIs
As Lori McVittie describes: "DevOps has, at its core, a pillar based on measurement. Measurement of KPI (Key Performance Indicators) relative to operations like MTTR (Mean Time to Recover) and Lead Time to Change."
These measurements are the core building blocks for starting a DevOps Scorecard, especially LTTC - Lead Time to Change. How fast can DevOps implement new features is the primary question.
Helpfully Lori discusses these parameters within a practical context of describing the relationship of container technologies.
DevOps Capability Map
|Agile Business Architecture||
||These faster models for software development can be accelerated through an enabling suite of Cloud components, particularly at the PaaS layer, that provide the automation building blocks for speeding developer productivity.|
||CD is a methodology for software development that emphasizes a high frequency, continual and ongoing process of merging different code projects.|
|Enterprise PaaS||These faster models for software development can be accelerated through an enabling suite of Cloud components, particularly at the PaaS layer, that provide the automation building blocks for speeding developer productivity.|
|Cloud Management Platform||
||A core engine for composing application deployment templates and managing their execution across multiple Cloud providers.|
Solution Blueprints define how these best practices can be repeated, through:
- Implementation Recipes - Business model and transformation templates.
- XaaS Mapping - Aligning process requirements to the relevant IaaS/PaaS/SaaS permutations.
- Solution Directory Profiles - Technology and vendor implementation options and examples.