Over the last few posts I’ve been discussing some of the things SAP IT teams will need to address on their journey to accelerated SAP change delivery. In my previous post I explained the need for process maturity and process automation. This time, we will look at the value of multi path development and release management.
During our conversations with existing and prospective SAP customers, we’ve noticed that almost all customers fall into one of four SAP change and release management profiles. 1. No ITSM automation and no SAP change control automation, 2. ITSM automation but no SAP change control automation, 3. ITSM automation and independent SAP change control automation, 4. Integrated ITSM and SAP change control automation. Do any of these profiles seem familiar for your organization?
During recent months, I’ve worked with several customers to implement Release Management strategies alongside a cloning strategy to reapply/retrofit changes to parallel tracks. The introduction of the Release Management Workbench within Rev-Trac has created so many new possibilities for managing changes and parallel project tracks. A common theme that seems to be coming up quite a lot, is around the process of getting changes from a parallel project track into the support track after Production go-live.
Rev-Trac 7 has introduced the Release Management Workbench, which allows organizations to bundle change tickets and manage many changes as a single release. This feature has been well received amongst RSC’s customers, however there are now advanced scenarios for consideration when utilizing this highly efficient approach.
We’ve published the last of our four-part SAP Change Control eNews series on Release Management change strategies, and in it I provide a detailed look at how Rev-Trac 7 significantly streamlines managing change requests into releases through reducing an 11 click process down to only two. Do you know another change automation tool that can trim the clicks needed for common Release Management procedures by 80% or more? Because I haven’t run across any.
ASUG presentations and papers are great sources of thoughtful and accurate information on current SAP strategies and trends. When I have a few spare minutes, I like to browse resources in the ASUG University just for the ideas and perspectives they offer. The other day I noted a detailed best-practices presentation by Wayne Kline and T.J. Wilson of Dublin-based Perrigo Company, on their company’s Release Management program. I was struck by how hands-on the procedures were, even with quite a lot of process automation.
Every strategy has its keys to success and an SAP change and release management strategy is no different. So if you’ve got a minute, take a quick look at this 1 minute video to hear three key factors we have noticed that could make a real difference to the success of your SAP release management strategy.
Every SAP user can benefit from a Release Management strategy, though they can be a challenge to set up. But what is the potential benefit? What’s the big payoff?
The answer at your own company will depend most of all on the size and complexity of your SAP infrastructure. Most companies with successful Release Management plans needed to smooth out change processes that had become cumbersome and hard to manage or were looking to accelerate change delivery.
Did you know that using Rev-Trac automated release management techniques can reduce the volume of individual request approvals needed to migrate large volumes of transports? When companies are looking to accelerate the pace of IT change delivery this can be a significant step in the right direction.
Have you felt lately like Alice in the Red Queen’s race? That’s when you have to run as fast as you can to stay in the same place. To get somewhere else, you have to run even faster. If you’ve been rushing harder and harder to keep up with changes coursing through your SAP systems, there’s a reason. IDC says companies push through twice as many changes now as they did in 2011. The pace will double again by 2017, they predict.