I’ve been briefing analysts these last few weeks, primarily those in the ALM, DevOps or ITSM practice areas. It’s an exercise I really enjoy. Not only does it offer an opportunity to find out what is top of mind for analysts (i.e. customers) but it also helps validate our approach to businesses and organizations.
We’ve been having more frequent conversations with SAP customers about “checking the box” when it comes to SAP change management. In this regard, checking the box means having a solution in place just so you can say that a solution is in place. As a customer’s SAP change management processes mature, they realize that their processes need to improve – maturing from a solution which meets the minimum requirements of audit, compliance and safety (e.g. for SAP Production systems), to a solution which supports the business with agile, continuous delivery capabilities.
“It’s not the strongest of the species to survive, nor the most intelligent, but the ones more responsive to change.” – Charles Darwin. Rev-Trac change control automation functionality can help your processes evolve naturally. Here are some ways cited by RSC customers…
Best practice SAP change control processes are not best practice if they can be worked around. Unless you can enforce your change control processes, there are a number of risks you will need to find ways to mitigate. So if you’ve got a minute, take a quick look at this 1 minute video to hear these risks.
Our July SAP Change Control eNewsletter continues our series about setting up efficient SAP Change processes that keep complex SAP systems stable. How do you implement new processes without sowing confusion? Usually, the best approach to guiding new change processes is to appoint the right people to a CAB (Change Advisory Board) that guides and enforces your SOP processes, keeping the flow of change stable and orderly.
Our June SAP Change Control eNewsletter just out, continues our series on creating business-efficient SOPs (standard operating procedures) for change control process that can keep complex SAP systems stable. This month’s article covers shifting from planning to actually designing a formalized SOP that will help keep your systems steady.
Process design takes time but can be worth every minute when crafting your SAP change control SOP (standard operating process). The PMO (project management office) generally crafts standards, identifies economies of repetition in project execution, and ultimately may even automate them. The PMO’s process design leads to creating the SAP change control SOP.