The benefits of SAP DevOps initiatives are well documented. Top of the list is massive improvements in speed and volume of SAP change with substantially reduced risk.Yet, pursuing an SAP DevOps strategy can be difficult for companies and SAP IT teams. Traditional SAP application development processes relied heavily on slow, old-fashioned manual tasks – many still in use today – and suffered from costly production outages.This is why we developed Rev-Trac – to eliminate error-prone manual tasks and replace them with automated and consistent processes to accelerate SAP application development without breaking production.
Chris Drake is Director of Products and Services, at Rev-Trac
He first joined the company in 2007 on the front line in customer support. In the role, he gained a comprehensive knowledge of the concerns and priorities customers have from both a user and strategic decision-maker standpoints. Working in the field as an implementation consultant, Chris has a deep understanding of SAP and change management and the impact manual processes have on SAP systems stability.
Chris’s insights, experience and the customer relationships he built in various positions on the support team provide a solid foundation for his role as product manager. He has vast knowledge to draw on to understand what the markets need and determine product direction.
Outside Rev-Trac, Chris is a fitness and sport enthusiast. He likes to exercise and spends time playing ice hockey and snowboarding.
Wisdom crafted by Chris Drake
Today, in the final blog of the SAP change management journey series, I look at the critical elements to achieve successful outcomes during the deploy phase of SAP application delivery. Here I will discuss the importance for the control of, and visibility into multiple SAP changes as your organization prepares for production deployment.
In order to master SAP change management, SAP IT teams need to deliver more change, more frequently with less risk. Making it essential to leverage tools for assessing readiness and quality of changes with predictable outcomes for release deployment to production. This ensures the quality of the build is consistent across all phases of the delivery process.
Following on from the previous blog, I continue looking at how businesses can master SAP change management to achieve successful outcomes during the various phases of application delivery. Here I will explore the requirement for automation, safety controls and collaboration during the build phase.
Mastering SAP change management is vital if organizations are to respond quickly to the constant shifts in business needs in today’s digital world. To keep pace with demand, eliminating manual SAP change management processes are crucial. Automation increases the velocity, volume and quality of SAP changes without breaking production.
Agile is a term that SAP IT teams are hearing more frequently these days. It shouldn’t come as a surprise. Today, businesses across every sector, must react quickly to constant changes in the marketplace to survive. However, to understand why agile is such a hot topic, you need to know something about the benefits of agile for SAP solutions.
Apple started a revolution with the concept of an app on the first iPhone. It has been interesting to see the impact it has had on different organizations’ product evolution.
When I turned on my first iPhone, I was confused. The phone function is just an app now. How does it get the same amount of real estate as the calendar? A different app for messaging and another for Internet – this was revolutionary.
In today’s fast-paced digital economy, there is a growing movement towards agile methodologies and DevOps for SAP. Increasingly, businesses are demanding more changes, more frequently with no loss in quality to meet the needs of customers, suppliers and partners.
Join the thousands of people that keep up-to-date with Rev-Trac
Join the Rev-Trac newsletter and we'll keep you informed of the new articles, resources and updates.
A frequent exercise for many SAP organizations is to refresh SAP QA Systems from Production. This ensures that suitable and up-to-date data is available for testing. With testing becoming increasingly important the need to refresh QA Systems is also on the rise.
In the current environment, we are seeing pressure on different businesses to conform to modern types of process standards and methodologies for building and deploying change. The current trend seems to have created demand for DevOps, Agile and Release Management controls. However, some organizations do not require the rapid style of change delivery offered by DevOps and Agile and are still happy to conform with process standards set out by ITIL and traditional release deployment strategies such as Waterfall.
It can be difficult keeping SAP landscapes consistent. For example, as Quality Assurance environments are refreshed, over time systems can begin to get out of sync. The number of DEV system transports existing only in the development system, unlikely to ever be moved to Production, grows.
Large organizations with high volume of changes, often experience many challenges around the sequencing of their transports. This can take a huge toll on an organization’s Basis team when managing the sequence to ensure that day-to-day support changes or large projects experience successful and safe production go-lives. In this month’s article, I would like to…
It’s interesting to observe how different organizations handle innovation in different ways. For some, innovation is infrequent and for others, innovation is ongoing and seemingly never ending.
As always, SAUG Summit is a great opportunity to catch up with customers and other Australian companies running SAP. In particular, to talk about their experiences and future plans and their progress towards automating their SAP DevOps Toolchain. When I was walking around the exhibition hall talking to the other exhibitors several common themes emerged. Namely, SAP DevOps, Agile Development and Digital Transformation. All reflecting the growing trend among SAP IT support teams to increase the volume of change and increase the speed at which it is delivered.