I’ve worked specifically in SAP change management for more years than I care to mention, and one thing I’ve heard repeatedly is the need for a reliable method of checking inter-object dependencies between transports.
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.
After many years analyzing customers’ change control processes we’ve learned that no two processes are ever the same. However, I’ve noticed that when a company sets out to improve their change control processes, they tend to make them more complex than necessary. Particularly when attempting agile processes for the first time.
