Recently at a customer site we discovered a great use case for the Project Release field when used in conjunction with Release Management. This organization required 2 different change types. Firstly, changes to be deployed in the morning. These changes having been assessed to not impact production stability. Secondly, other changes to be deployed in the evenings. Changes that couldn’t be introduced while the business is using the production system. In this case, the developer could determine whether the change required morning or evening deployment and could assign the schedule.
Most expanding SAP IT teams eventually run into trouble getting projects and other changes out the door fast enough to keep up with new change requests coming in. Often, the change teams are caught in a “boiling frog” situation. According to the fable, if you put a frog in a pot and steadily increase the water temperature, the frog won’t notice until it’s too late to jump back out. That’s what drives most new Release Management strategies, but those can be a real challenge to set up.
Accelerating SAP change delivery has become very important. Since 2011, change volumes have doubled. We’ve confirmed this with our customers. They tell us business innovations and changing economic environments play a part but the biggest challenge is that change must be delivered ever faster. This is not particularly new – but the business need to adapt and respond very quickly keeps gaining momentum. As Charlies Darwin once said, “It’s not the strongest or most intelligent who will survive but those who can best manage change.”
With DevOps becoming mainstream, managing SAP changes by frequent release can’t afford to be an aspiration any longer – it needs to become a tangible goal. So if you’ve got a minute, take a quick look at this 1 minute video to hear what we recommend for your Delivery Tracks and Development Streams.