Lesson 4 of 5
Transformation workstreams
8 min
A transformation program is many projects running in parallel, each with its own specialists, deliverables and risks. They are usually organized as workstreams. Knowing them helps you see where your work fits, whom you depend on, and why so many problems show up only when the workstreams meet in testing.
The workstreams
| Workstream | What it delivers | Contoso example |
|---|---|---|
| Process and functional design | Target processes, configuration and fit-to-standard or fit-gap decisions | Order-to-cash design for fleet customers, owned by Maria |
| Custom code | Analysis, retirement, adaptation and testing of custom developments | Custom finance reports replaced by standard apps; remaining code adapted |
| Data | Data migration or conversion preparation, cleansing and validation | Business partner preparation and financial data checks |
| Integration | Interfaces to and from other systems, adapted and tested | EDI orders from fleet customers; bank interfaces |
| Security and roles | Business roles, Fiori catalogs, authorizations, segregation of duties | New roles for Maria's order-to-cash team |
| Analytics and reporting | Embedded analytics, reports and data warehouse changes | Margin reporting for CMC-ALT-100 |
| Technical and Basis | Landscape, sizing, system builds, technical conversion, operations | Private Edition landscape under RISE with SAP |
| Change and training | Communication, training, readiness of users | Training for plants 1710 and 1720 |
| Testing | Test strategy, test cycles, evidence and sign-off | Priya's master test plan |
| Cutover | Cutover plan, rehearsals, go-live and hypercare | Luis's cutover runbook |
Typical workstreams in an SAP S/4HANA transformation program.
Workstreams are not independent. A process decision changes configuration, which changes roles, test cases and training. A data rule changes what reports show. An interface change needs an integration test with a partner system. The PMO's job, Grace's job at Contoso, is to keep these dependencies visible and to make sure decisions reach every workstream they affect.
The methodology frame
Most SAP programs follow SAP Activate, SAP's implementation methodology, which organizes work into phases. The workstreams run across those phases, and each phase ends with a quality gate that checks the deliverables before the program moves on.
- DiscoverUnderstand the value and the options; build the case for change
- PreparePlan the project, set up governance, team and systems
- ExploreFit-to-standard workshops; design decisions and backlog
- RealizeBuild and configure in sprints; unit, string and integration testing; data loads
- DeployAcceptance and final testing, cutover, go-live
- RunHypercare, operations and continuous improvement
Where the workstreams meet
Most workstreams deliver pieces that cannot be judged in isolation. A business role is only right if the user can run the process. A converted custom report is only right if its numbers match. An interface is only right if the partner system accepts what it sends. The place where all the pieces meet is testing: integration testing, user acceptance testing and the cutover rehearsals. That is why the test workstream needs input from every other workstream, and why its plan is a good map of the program's real progress.
Workstreams also differ by transition path. A new implementation puts more weight on process design, data migration and training, because everything is rebuilt. A system conversion puts more weight on custom code adaptation, data preparation in the old system and technical conversion rehearsals, because the existing system is carried forward. Either way, every workstream ends up in the same place: the test plan, the cutover plan and the go-live decision.
What would you do?
In Contoso's Realize phase, the custom code team retires a custom pricing report and replaces it with a standard app. Nobody informs the training team or Priya. What is the most likely consequence?
- Typical workstreams: process, custom code, data, integration, security and roles, analytics, technical, change and training, testing, cutover.
- Workstreams depend on each other; the PMO keeps decisions and dependencies visible.
- SAP Activate phases: Discover, Prepare, Explore, Realize, Deploy, Run, with quality gates.
- Testing is where all workstreams meet and are proven together.
Check your understanding · not graded
Lesson check
1. Which is not a typical workstream of an SAP S/4HANA program?
2. Which SAP Activate phase holds fit-to-standard workshops?
3. Who owns keeping cross-workstream dependencies visible at Contoso?
4. Why is testing described as the place where workstreams meet?