SAP Activate is a methodology designed to streamline SAP implementation projects by leveraging an agile approach. By organizing work into sprints and waves, it provides the flexibility needed to adapt to changes, ensuring faster and more efficient project delivery. There are 6 phases available in this methodology:
1. Discover
4. Realize
2. Prepare
5. Deploy
3. Explore
6. Run
1. Discover
The Discover Phase is the first phase of the SAP Activate methodology. Its main goal is to help customers understand the value of SAP solutions and explore how they align with their business needs. During this phase, high-level requirements are gathered, and the project’s scope is defined. Customers also get an overview of SAP Best Practices, available tools, and deployment options (such as cloud, on-premise, or hybrid).
2. Prepare
The Prepare Phase is when the project gets ready to start. In this phase, the project team is formed, tools and systems are set up, and the project plan is created. Key activities performed in this phase include:
Project team will be prepared by managers/directors.
Finalizing the project plan.
Assign roles & responsibilities to to module-specific consultants.
Plan for Fit-to-Standard workshops (coming in Explore phase).
Conducting the project kickoff meeting between the technical team and business stakeholders (core business team).
3. Explore
The Explore Phase focuses on understanding how SAP’s standard processes fit the business needs. Teams conduct workshops, identify gaps, and plan for the upcoming configuration and testing work in the Realize Phase. Key activities include:
Conduct Fit-to-Standard workshops – Identify gaps between standard and customer-specific requirements.
Configuration planning – Assign the tasks to the module specific consultants.
Planning of sprint and wave strategies.
Test planning – We need to plan the testing scope ready for upcoming Realize phase.
Note:
Backlog: A backlog is a prioritized list of tasks, features, enhancements, and requirements that need to be completed during a project. It acts as the single source of truth for what the team plans to work on.
4. Realize
The Realize Phase is where the project team configures the SAP system based on the requirements gathered earlier. The team builds and tests the solution in iterative cycles (sprints), making sure the system meets business needs and any gaps identified are addressed. This phase prepares the project for final deployment.
Actual Configuration, customization, development, and testing are performed based on the sprint plan defined.
Development includes RICEFW objects, where both functional and technical consultants collaborate to design and build.
Get user sign-off after successful testing and validation.
Plan data migration and cutover activities (to be executed in the Deploy Phase).
Key notes about Sprint and Wave:
Sprint: A sprint is a short, fixed period—typically 2 to 4 weeks—during which a team works iteratively and incrementally on a specific set of tasks or features, aiming to deliver a functional piece of the project by the end.
Wave: A Wave is a broader phase or segment of a project that groups together related activities, often containing multiple sprints. It is used to manage and deliver large projects in staged, manageable parts.
Example for Waves and Sprints in the Realization phase:
5. Deploy
The Deploy Phase is when the system goes live. All final preparations are made to move from the test environment to the production system. This includes executing data migration, performing cutover activities, and ensuring that the business and support teams are ready.
Importing finalized transport requests into the production system (Probably on weekends).
Perform cutover activities – Uploading master/transactional data into production system.
Production System Readiness – Ensure system, data, and users are fully prepared.
Go-Live – Make the system available to users for live operations.
Support Readiness – Hypercare planning
6. Run
The Run phase is the final phase of the SAP Activate methodology. It begins after go-live and focuses on keeping the system stable, supporting users, and continuously improving the solution. Key points:
Agile approach – SAP Activate combines SAP Best Practices, guided configuration, and Agile methodology to help deliver S/4HANA projects efficiently. The Agile approach allows teams to work in short, iterative cycles (called sprints), enabling faster feedback and continuous improvement.
Traditional Waterfall – It is a linear, sequential approach where each project phase is completed before the next begins. The ASAP methodology follows this waterfall approach, emphasizing detailed upfront planning and step-by-step execution with limited flexibility for changes once phases are finalized.
Deployment options:
Cloud – In a cloud deployment, SAP is hosted on external servers managed by SAP or a cloud provider (like AWS, Azure). You access it over the internet. No need to buy/manage hardware, faster setup, subscription based pricing. We have 2 cloud types:
Public Cloud: Your system runs on a cloud platform shared with other customers. This is the environment used in Grow with SAP.
Private Cloud: Dedicated environment: Your system runs on private infrastructure (but still hosted by SAP or a provider). This environment mostly used Rise with SAP.
On-premise – In an on-premise setup, SAP is installed on your company’s own servers and infrastructure.
Just need to buy one-time license with maintenance costs,
Clients will have Full control over system and customizations
Hybrid – A hybrid model combines both cloud and on-premise systems. Offers flexibility and gradual transformation. Useful for companies moving to the cloud in stages. Core systems may stay on-premise, while innovations run in the cloud
RISE with SAP – It is a Business Transformation as a Service (BTaaS) offering that helps companies move to SAP S/4HANA — at their own pace — with a single contract and flexible deployment options (private cloud or public cloud).
GROW with SAP – It is a solution package designed specifically for mid-sized companies and fast-growing businesses that want to adopt SAP S/4HANA Cloud (Public Edition) quickly and efficiently.
String Testing – It refers to testing a sequence of related transactions that reflect a complete business process (End to End flow) — for example, from Sales Order to Billing or Procure to Pay.
Example: P2P Cycle – PO creation, MIGO, MIRO, Vendor payment.
