Lesson 2 of 6
SAP Activate in one hour
10 min
SAP Activate is SAP's implementation methodology for SAP S/4HANA. It combines ready-to-run business processes (SAP Best Practices), guided configuration and an agile, phase-based way of working. Whether Contoso's system integrator calls its plan "Activate" or something else, the structure is almost always the same six phases. Knowing them tells a key user when they will be busy and what is expected at each point.
- DiscoverUnderstand what S/4HANA offers and build the case for change
- PrepareSet up the project: team, plan, governance, systems, onboarding
- ExploreFit-to-standard workshops; identify gaps and configuration values; build the backlog
- RealizeConfigure and build in sprints; test; prepare data, training and integration
- DeployFinal testing, end-user training, cutover, go-live and hypercare
- RunOperate, support and improve the live system
Between phases, projects hold quality gates: formal checks that the phase's deliverables are complete before moving on. For a key user, quality gates are a useful signal. If you are asked to confirm that the design for your area is complete at the end of Explore, that is a real commitment, not a formality.
Where the key user carries the load
| Phase | Key user tasks | Load |
|---|---|---|
| Discover | Usually not yet involved; may contribute pain points and volumes | Low |
| Prepare | Nominated; onboarded; learns SAP basics and the project way of working | Low to medium |
| Explore | Attends fit-to-standard workshops; provides examples; reviews designs; documents requirements and gaps | High |
| Realize | Validates configuration in sprint reviews; tests; supplies test data; learns the solution deeply; prepares training | High |
| Deploy | User acceptance sign-off support; trains end users; cutover tasks; first-line support at go-live | Very high |
| Run | Department expert; handles questions and change requests; tests updates | Medium, ongoing |
- Months 1–2PrepareMaria is nominated, trained on SAP basics and given access to the Best Practices system
- Months 3–5ExploreOrder-to-cash fit-to-standard workshops; backlog of requirements and gaps for sales
- Months 6–11RealizeSprint reviews, integration tests, user acceptance tests, training material
- Months 12–13DeployEnd-user training, dress rehearsals, cutover, Q3 go-live, hypercare
- Month 14 onwardRunOrder desk expert; regression testing for each SAP update
Agile in Realize
SAP Activate runs the Realize phase in short iterations, often called sprints. The backlog from Explore is split into pieces, configured and built, and shown to key users in sprint reviews. This is where key users have the most influence on the outcome: a mistake spotted in a sprint review costs an hour to fix; the same mistake found in user acceptance testing costs days, and after go-live, weeks. Attend sprint reviews with real cases in hand, not just to watch a demo. Before each review, ask the consultant which backlog items will be shown and prepare two or three cases for each: a normal one, an awkward one and one that should be rejected by the system. After the review, check that your feedback was recorded against the backlog item. Feedback given only verbally in a demo is easily lost when the sprint closes.
Workstreams
Activate also organizes the project into workstreams that run across the phases: project management, application design and configuration, data management, integration, testing, organizational change management and training, technical architecture and others. A key user mainly works with application design (workshops, requirements), testing, data (validating migrated records) and change and training. Knowing the workstream names helps you find the right person when something goes wrong. For example, a customer that is missing after a test load is a data management question; an invoice that never reaches the customer portal is an integration question; a confusing training exercise is a change management question.
What would you do?
In a Realize sprint review, the consultant demonstrates sales order entry for Contoso. Maria notices that the demo uses a customer without a fleet contract, while 70% of real orders reference one. What should she do?
- SAP Activate phases: Discover, Prepare, Explore, Realize, Deploy, Run.
- Quality gates check each phase's deliverables; your confirmation at a gate is a real commitment.
- Key user load peaks in Explore, Realize and Deploy.
- Sprint reviews in Realize are the cheapest place to catch design errors.
Check your understanding · not graded
Lesson check
1. In which SAP Activate phase do fit-to-standard workshops primarily take place?
2. In which phase are cutover and go-live?
3. What is a quality gate?
4. Why should key users attend sprint reviews with real cases?