SAP systems
Before we look at whether SCRUM and SAP are compatible, let's take a look at the special features of SAP: SAP's systems were undoubtedly a milestone in the field of ERP software!
SAP innovations enable customers around the world to collaborate efficiently and leverage business insights.
What makes SAP projects special
The individual SAP modules are closely interlinked and map the entire company processes in one system.
This means that all departments, employees and decision-makers are usually affected by an SAP implementation project. This already indicates the size and scope of SAP implementation projects in organizations.
Reading tip: Klaus Wybranietz
SAP, The Agile Way
Agility in SAP projects - is that possible?
For a long time, such projects were traditionally carried out using the waterfall model. Many SAP project managers are of the opinion that the agile Scrum approach is not suitable for the introduction of such a system.
The agile approach to project organization focuses strongly on the product and the close collaboration of the people involved in its creation. This is in complete contrast to the fully planned phases of the classic approach, in which only certain activities may be carried out.
SCRUM in SAP projects?
A clear YES: We can confirm this from our experience in past projects: Agility works extremely well for successfully implementing SAP projects. Scrum is a good framework for successfully implementing SAP projects in an agile manner.
Why? "SCRUM is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions to complex problems" - Scrum Guide Scrum Guide

Why SCRUM makes sense for SAP implementation
SAP projects are complex
The implementation of an SAP system is a very complex project. This is exactly what Scrum is designed for:
The Scrum Guide describes this as follows: "We are pursuing the increasing use of Scrum in an ever more complex world. Scrum uses an iterative, incremental approach to optimize predictability and control risk".
Scrum relies on groups of people who collectively have all the skills and expertise to get the job done and to share or acquire such skills when needed".
Development in SAP projects
Many SAP project managers reject Scrum because "no development takes place". Instead, they prefer to rely on the standard SAP software - which means that individual functions are rarely developed from scratch.
In September 2017, Jeff Sutherland and Ken Schwaber clarified in the Scrum Guide that by "development" they don't just mean programming, but any kind of complex work. Organizations create detailed schedules with milestones, topics and interfaces.
SCRUM is scalable
SAP projects are powerful, involving many teams with different focuses and an extremely high need for integration.
The Scrum Guide states: "Scrum relies on groups of people who collectively have all the skills and expertise to do the work and share or acquire such skills as needed".
Scaled Scrum frameworks such as Scrum@Scale, Nexus or SAFe help with the integration of many teams.
SCRUM can be planned
The Scrum Guide explicitly describes the sprint planning:
"Sprint planning initiates the sprint by setting out the work to be carried out for the sprint. This resulting plan is created through the collaborative work of the entire Scrum team."
Individual teams are already planning agile work.
If several teams work together, additional planning levels are added. The difference to waterfall projects: Planning does not just take place once at the start of a project, but at regular intervals.
Scrum is possible with globally distributed teams
Remote working in SAP projects with Scrum is absolutely possible with distributed teams. We have experienced this positively ourselves in our projects.
It is important to define the framework and tools for the project participants. This lays the foundations for distributed collaboration, which is based on the following values: openness, courage, respect, commitment and focus (Scrum Guide).
"Long-term planning works best in the short term." - Euripides