A lot has changed in the last 12 months.
With digital transformation projects in the forefront of people’s minds the need to modernise IT systems and processes has never been as critical as it is today. The speed at which software can change and deliver innovation is now the speed at which the business, and your competitors, can adapt to new market conditions. There’s immense pressure to change and those who don’t or can’t will struggle to survive.
Businesses are already recognising this need and according to data from Forrester Research presented in a Basis Technologies webinar earlier this year…
“75 per cent of software decision makers surveyed believe that modernisation of key legacy applications is a critical or high priority, whilst 68 percent see the update to a new release of packaged applications, such as SAP, in the same way.”
It’s not surprising then that the number of calls and meetings that fill my week to talk specifically about DevOps has gone through the roof.
In fact, The Right Scale State of the Cloud survey found that over 81% of surveyed enterprises have already adopted DevOps in some parts of their organisation.
What’s happening now is that more and more companies want to talk about applying DevOps to their SAP applications and are genuinely interested in the what, why and how.
So what does DevOps for SAP mean?
For those who are not up to speed on DevOps I’ll briefly explain what it’s about.
It’s essentially a more collaborative method of delivering applications where traditional organisational silos are replaced by cross-functional, multi-skilled teams that are focused around business outcomes.
This, along with the high levels of automation involved in the process, provides companies with the agility they need to keep pace with the changing demands of the business. In terms of application delivery that means they can achieve a faster time to market, higher quality, and lower costs, whilst reducing risk.
An IBM study found that the adoption of DevOps has been seen to…
Increase software delivery speed by up to 1,600 per cent.
whilst Puppet have stated that DevOps can bring…
60 times fewer failures with organisations twice as likely to exceed their profitability, market share and productivity goals.
But without DevOps, deploying even small changes to SAP systems can take a huge amount of time due to outdated and long release cycles along with concerns about risk and stability. SAP customers who’ve adopted DevOps ways of working, on the other hand, are now able to deliver in much shorter cycles, which translates to a big leg up on their competitors who are yet to see the light.
The foundations of DevOps
Some companies implement a ‘big bang’ approach to DevOps but it’s also possible to get there step by step. Either way, there are some core concepts that form the foundation DevOps is built upon. It’s important to understand them before you get started:
1. Agile Development
The concept of Agile development – where applications are delivered frequently, in short iterations – is vital. You can adopt Agile for SAP without making the step to DevOps, but DevOps won’t work without Agile.
I’ve talked a lot about Agile for SAP in other posts so I won’t go into details here but feel free to read those to get more of an insight.
Where Agile scores highly is in bringing together development, testing and the business, but there’s a gap if you don’t have the ability to bring automated deployment and automated environment provisioning to the table. This is where DevOps comes in to add value to the entire process from requirements through to business delivery.
2. Collaborative Culture
You can’t underestimate how important it is to to understand the cultural and organisational changes involved in the implementation of DevOps.
As I mentioned earlier, the biggest change is a reorganisation of teams to move away from the ‘silo’ job functions of development, testing, operations (basis) and security towards mixed discipline teams that constantly work with the business to deliver what it needs.
Management sponsorship and buy-in is vital here to support what may be a challenging transition, so that adapting to new roles feels safe and rewarding.
The roles of pretty much everyone will be affected to a greater or lesser degree. People should be encouraged to take on more responsibility and to blur the boundaries imposed by their traditional roles.
3. The right toolsets
Of course it’s critical to look at tooling to support your DevOps processes and to deliver the levels of automation that bring so many benefits.
You’ll hear people talking about a DevOps toolchain and it’s important to recognise that no one single tool will support all the facets of DevOps.
You therefore need to look at how you’ll manage the key parts of DevOps from requirements through to the processes of continuous integration, delivery, deployment and improvement.
In SAP you need to look at how you can use tooling to support:
- Automation of unit and regression testing
- Improvement in code quality
- Management of the sequencing and dependencies between changes and transports
- Enforcing risk, quality and impact checks
- Provisioning environments for testing
- Automating the deployment of transports and rollback in the case of failure
- Measuring the performance of development and testing teams
So the need is understood, but what about the reality? Change can be difficult, particularly in complex, business-critical software environments such as SAP. Even firms that see the logic of developing and updating their systems may be reluctant to take on transformation initiatives that have in the past been regarded as disruptive projects, potentially loaded with risk.
As one of our customers who have successfully implemented DevOps have said…
“It’s a better way of working. We don’t need any survival anxiety to show it is a better way of working. We know it reduces risk – delivery risk – and we know it increases quality”.