Lesson 6 of 6
Fitting SAP Activate and Cloud ALM
10 min
Listen to this lesson
A TCoE that works in its own vocabulary will be ignored by projects that work in SAP Activate. The last piece of the operating model is to map TCoE services onto SAP Activate phases and onto the SAP Cloud ALM apps that projects and releases already use, so that engaging the TCoE feels like part of the method, not an extra step.
TCoE services by SAP Activate phase
| Phase | What the project does | TCoE service |
|---|---|---|
| Discover | Explores scope and value | Release assessment input; demand forecast for the TCoE plan |
| Prepare | Sets up the project, plan and tools | Engagement tier agreed; test architect named; Cloud ALM test standards applied |
| Explore | Fit-to-standard, backlog, test strategy and planning | Project test strategy from the TCoE template; regression impact identified |
| Realize | Builds in sprints; unit, string, integration, data migration and UAT | Test data recipes, regression runs, UAT facilitation, evidence review |
| Deploy | Cutover and go-live | Readiness assessment; dress rehearsal checks; regression of shared processes |
| Run | Operates and improves; regression for each change | Regression pack updated with the project's new tests; hypercare support |
TCoE services mapped to SAP Activate phases. SAP's learning material places formal integration and data migration tests in Cloud ALM, UAT in Realize and regression in Run.
- PrepareEngagement tier agreed; test architect named; Cloud ALM conventions applied
- ExploreProject strategy from the TCoE template; regression impact listed
- RealizeData recipes, regression runs on shared processes, UAT facilitation
- DeployReadiness assessment; new tests handed into the pack
- RunHypercare support; project closed only after the pack handover
Agree one convention for how work maps to SAP Cloud ALM and write it into the playbook: which Cloud ALM project holds the maintained regression pack, how each release event gets its own test plans, how test cases are named and linked to processes, requirements and user stories, and which quality gates every release passes. The convention matters more than the exact choice. Without it, each project invents its own structure, and the TCoE cannot report coverage or trends across releases.
The handover in Run is the step projects most often skip. A project's new end-to-end tests must join the TCoE regression pack before the project closes, with an owner, data recipe and risk ranking. Write that into the project's exit criteria for Deploy, or the pack will stop reflecting how Contoso actually works.
SAP Cloud ALM apps and TCoE roles
| SAP Cloud ALM app | What it holds | Main TCoE users |
|---|---|---|
| Test Preparation | Manual test cases built from activities and actions; automated test cases from connected automation providers; links to requirements and user stories | Test architects, automation lead |
| Test Plans | Which test cases run in a cycle, assigned testers, dates; status In Preparation, In Testing, Finished | TCoE lead, test architects |
| Test Execution | Step results, evidence and defects raised from a run | Key users, test analysts, partner testers |
| Defects | Defects recorded against test runs, with their workflow | All roles; developers fix |
| Quality Gates | Checkpoints where the project is assessed before moving on; can be imported from SAP Activate roadmaps | TCoE lead, PMO |
| Traceability and Analytics | Coverage per requirement or user story; test execution analysis | TCoE lead, process owners |
SAP Cloud ALM test management apps as described in SAP Help, and who in the TCoE uses each.
From Solution Manager vocabulary
Contoso's ECC support team still thinks in SAP Solution Manager 7.2 terms. SAP's Cloud ALM help maps them: a Solution Manager test package corresponds to a Cloud ALM test plan, the Test Suite to test and defect management, test steps to test activities and actions, and the testing expert role to the test coordinator. Publishing that mapping in the TCoE playbook saves weeks of confusion as ECC test assets are triaged before the end of Solution Manager mainstream maintenance in 2027.
| SAP Solution Manager 7.2 | SAP Cloud ALM |
|---|---|
| Test package | Test plan |
| Test Suite (test and defect management) | Test management and defect management apps |
| Test step | Test activity and action |
| Testing expert | Test coordinator |
What would you do?
The warehouse project is ready to close after go-live. Its 40 new end-to-end tests sit in the project's own SAP Cloud ALM project, without data recipes or risk ranking. The project manager wants to release the team on Friday. What should Priya insist on?
- Map every TCoE service to an SAP Activate phase so engagement feels like part of the method.
- Make "new tests join the regression pack" an exit criterion before the project closes.
- Know the Cloud ALM apps: Test Preparation, Test Plans, Test Execution, Defects, Quality Gates, Traceability and Analytics.
- Publish the Solution Manager to Cloud ALM terminology mapping for teams moving from ECC.
Check your understanding · not graded
Lesson check
1. In which SAP Cloud ALM test plan status can testers execute test cases?
2. Which step do projects most often skip at the end of SAP Activate?
3. What does a Solution Manager test package correspond to in SAP Cloud ALM?
4. How should the TCoE treat the Joule testing agents listed in SAP Cloud ALM help today?