Discovering the Workstreams


After completing this lesson, you will be able to:

  • Identify the Workstreams
  • Analyze the project management workstream
  • Discover the design and configuration workstream
  • Illustrate the workstream for analytics
  • Describe the customer team enablement workstream
  • Illustrate the solution adoption workstream
  • Illustrate the extensibility workstream
  • Summarize the testing workstream
  • Illustrate the integration workstream
  • Illustrate the operations and support workstream
  • Analyze the data management workstream
  • Illustrate the technical architecture and infrastructure workstream

Introduction to Workstreams

SAP Activate Methodology proposes a set of workstreams for you to organize your work and establish the team’s structure. That doesn’t mean that depending on the project, some workstreams cannot be split into sub streams or in some cases, merged.

Each roadmap available has a proposed structure that addresses or emphasizes the specifics of each implementation. Most roadmaps are for implementation projects for different products, some guide you across upgrade projects. One characteristic of the roadmaps is that they are industry agnostic. For those working in SAP implementations, you might remember the model company concept, or if you are currently working with SAP Best Practices, you will find packages specific for the public sector.

One example is for the SAP S/4HANA Cloud Edition, Public Sector.

The suggested workstreams are:

  • Project Management – Administrative operations, budget control, staffing up, overall control

  • Customer Team Enablement – Onboarding processes, solution, and product awareness

  • Technical Architecture and Infrastructure – IT design

  • Application Design and Configuration – Detailed solution design, configuration, security concepts

  • Extensibility – Development of additional functionalities

  • Integration – Interface design, communication across applications and businesses

  • Testing – Solution validation

  • Data Management – Data loading, data cleansing, data lifecycle management

  • Operations and Support – IT operations, end-user support processes

  • Solution Adoption – Training, organizational change management

  • Analytics – Data modeling, reporting design, and implementation

Project Management Workstream

Project Management can be seen as a generic workstream that addresses topics like:

  • Organization – How to structure the different teams that will take part in the project.

  • Governance – How to address roadblocks, how to reach consensus, how to escalate.

  • Standards – What to document, how to document, with what detail, which tools should the team use to document, test, and deploy, how to report and process incidents and change requests.

  • Budget – How resources should be allocated, how to consider a request for change and its impact.

  • Planning – How to approach the different project goals, will you use agile or a waterfall approach, most likely a hybrid approach between these two.

  • Signoff – How to verify if the project is ready to move on (QGates), with which criteria?

Project Governance

Project governance provides a framework in which the project manager and sponsors can make decisions that satisfy both stakeholder needs and expectations and organizational strategic objectives or address circumstances where these may not be in alignment.

© Project Management Institute, Inc. A guide to the project management body of knowledge PMBOK Guide. Sixth edition. 2017.

Project Governance includes:

  • Guiding and overseeing the management of project work
  • Ensuring adherence to policies, standards and guidelines
  • Establishing governance roles, responsibilities and authorities
  • Decision-making regarding risk escalations, changes and resources (e.g. team, financial, physical, facilities)
  • Ensuring appropriate stakeholder engagement
  • Monitoring performance

It is important in any project to have the standard definition of the Project Governance. It outlines the relationship between the different groups and stakeholders involved in the project.

The project governance describes the flow of information between the project and all the stakeholders. It specifies the decision making and escalation steps to resolve issues.

The governance framework has a couple of characteristics that need to be established. It focuses on realizing the business value, managing the risk and issues, and enforcing the standards and accountability for the project.

It needs to be aligned with the governance that the organization already has in place. It also has to ensure that communication and messaging fits the organization and stakeholder needs. Governance needs to be adjusted to each customer. There is no one size that fits all.

SAP provides tools to support the documentation and track the overall progress status. Traditionally, SAP Solution Manager was used but with the advent of cloud-based solutions, SAP Cloud ALM has become more common. For SAP S/4HANA cloud edition it’s recommended to use SAP Cloud ALM.

In an on-premise scenario, a project manager most likely will be using SAP Solution Manager to perform is documentation and tracking activities. In a cloud scenario, SAP Cloud ALM will be more common. The trend in SAP is to evolve from SAP Solution Manager to SAP Cloud ALM.

In a on-premise scenario a project manager most likely will be using SAP Solution Manager to perform is documentation and tracking activities, in a cloud scenario SAP Cloud ALM will be more common. The trend in SAP is to evolve from SAP Solution Manager to Sap Cloud ALM.

Both tools, SAP Solution Manager and SAP Cloud ALM can provide the single source of truth for the project documentation, for all workstreams. Solution Documentation has now been used for more than 20 years in SAP projects.

This tools functionality can cooperate with other products, SAP and no SAP, for different purposes from documentation, testing, process modeling … one example that is taking a major role in SAP implementations is SAP Signavio.

The Project Manager establishing the governance needs to identify the key players who will be a part of the governance and then build in the stakeholder group. Generally the key players are specified within the project contract or Statement of Work (SoW).

SAP Project Roles by Workstream

WorkstreamImplementation PartnerCustomer - BusinessCustomer - IT

Project Management

  • Project Sponsor

  • Project Manager

  • Project Administrator

  • Quality Manager

  • Project Sponsor

  • Project Manager

  • Project Administrator

  • IT Head

  • IT Project Manager

  • Quality Manager (Project Management)

Customer Team Enablement

Education Services Consultant


  • Team Training Coordinator

  • Trainee

Design and Configuration

  • Business Solution Architect

  • Application Consulting Lead

  • Application Consultant

  • Application Security Consultant

  • Business Process Owner

  • Business Process Expert

  • Key User

  • Business Solution Architect

  • Internal Application Consultant

  • Authorization Expert


  • Development Lead

  • Developer

  • Developer

  • Release Manager

  • Quality Manager (Extensibility)


Implementation Partner: Term covers SAP Digital Business Services as well as Certified SAP Partners.

SAP Project Roles by Workstream (Continued)

WorkstreamPartnerCustomer - BusinessCustomer - IT

Data Management

  • Data Migration Architect

  • Data Migration Developer

  • Data Volume Management Consultant

  • Business Data Owner (data custodian)

  • Data Preparation Expert

  • Master Data Change Requestor

  • Master Data Maintainer

  • Master Data Sponsor

  • Data Extraction Expert

  • DVM ALM Process Owner

  • Master Data Manager (data steward)


Integration Development Consultant


Integration Technology SME


  • Automation and Regression

  • Test Lead

  • Manual Testers

  • Performance Tester

  • Test Case Developer

  • Test Manager

  • Test Master Data Coordinator

Manual Testers

  • Manual Testers

  • Test Coordinators


Analytics Consultant

  • Analytics Architect

  • Analytics Consultant

Solution Adoption

  • Organization Change Management Consultant

  • Value Expert

  • End User Training Consultant

  • Training Materials Developer

  • Organization Change Manager

  • Organization Change Coordinator

  • End User Training Coordinator

  • End User

  • End User Trainer


SAP Project Roles by Workstream (continued)

WorkstreamPartnerCustomer - BusinessCustomer - IT

Technical Architecture and Infrastructure

  • Technology Architect

  • Technical Security Consultant

  • Technology Consultant

  • Basis Administrator

  • Technology Architect

  • IT Infrastructure Administrator

  • Technical SME

  • Basis Administrator

  • Database Administrator

Operations and Support

  • Solution Manager Consultant

  • ALM/CoE Management Consultant

  • ALM Sponsor / Head of CCoE

  • ALM Process Owner

  • Service Desk Expert

  • Service Desk Manager Solution Manager Administrator

SAP Project Governance Bodies

  • Level 1 - Executive Board

    • Sets business vision and goals

    • Approves project vision

    • Delegates authority to Steering Committee

    • Allocates funding for the project

  • Level 2 - Steering Committee

    • Approves project goals

    • Approves project results

    • Approves project changes according to delegated authorities

    • Delegates authorities to the Operating Committee

    • Escalates unresolved issues to the Executive Board

  • Level 3 - Operating Committee

    • Monitors and coordinates activities in all workstreams of the project

    • Delegates authority to Ongoing Meetings

    • Escalates unresolved issues to Steering Committee

  • Level 3 - Integrating Committee

    • Makes decisions on integration and master data management across projects

    • Defines integration and controls integration points register

    • Defines release strategy across projects

    • Ensures integration and consistency between deliverables of several projects

  • Level 4 - Ongoing Meetings

    • Clarifies ongoing open issues

    • Escalates unresolved issues to Level 3

    • Makes decisions as delegated by Level 3

SAP Project Roles by Governance Bodies

Governance BodyImplementation PartnerCustomer - BusinessCustomer - IT

Steering Committee

Project Sponsor, Project Manager, Project Administrator

Project Sponsor (Head), Project Manager, Organization Change Manager, Business Process Owner

IT Head, Project Manager, Project Administrator, technology Architect

Integration Committee

Project Manager, project Administrator, Business Solution Architect, Technology Architect

Project Manager, Key User

Project Manager, Project Administrator, Business Solution Architect, Technology Architect

Operating Committee

Project Manager, project Administrator, Technology Architect, Application Consulting Lead

Project Manager (Head), Organization Change Coordinator, Business process Expert

Project Manager, Project Administrator, Technology Architect, Internal Application Consultant

Ongoing Meetings




Access the SAP Signavio Process Navigator and SAP Activate Roadmap Viewer


  1. Access the SAP Signavio Process Navigator and browse the scope items for SAP S/4HANA Cloud.

    1. Access the SAP Signavio Process Navigator using, and browse the scope items for SAP S/4HANA Cloud edition, Public Sector.

  2. Open the SAP Activate Roadmap Viewer ( and choose the SAP SuccessFactors implementation roadmap. Review how the different workstreams have roles to play across the different phases. Would you keep this workstream breakdown? Would you merge or split? Look at Customer Team Enablement and Solution Adoption? Merge?

    1. Open the SAP Activate Roadmap Viewer using the link and look at the SAP SuccessFactors implementation roadmap

      Answer: It’s highly dependent on the project size and complexity. In a large project, splitting workstreams could take place. Just consider a global rollout where the extensions are built, some focusing on reporting, others in transactional operations. Customer team enablement in a smaller project can have the same players as solution adoption and in that case, why not merge both streams?

  3. Open the SAP Activate Roadmap Viewer ( and look at the SAP S/4HANA implementation roadmap. Why is the Customer Enablement absent?

    1. Open the SAP Activate Roadmap Viewer using the link and look at the SAP S/4HANA implementation roadmap.

      Answer: You will not always require all the workstreams. E.g. when you do the transition to S/4HANA one possible scenario is the system conversion. In this scenario the organization is moving from an existing solution to an evolution where much will look familiar. Customer Enablement has a more relevant role when a shift occurs into a new solution – one example: you have been running Human Resources in SAP ERP and now you move to SAP SuccessFactors, here the shift in features and functionality will be much stronger and therefore Customer Enablement work stream is strongly needed.

Explore the Demos and Trial Systems Available for SAP Cloud ALM


  1. Open the SAP support portal ( and explore the demos and trial systems available for SAP Cloud ALM.

    1. SAP support portal using explore the demos and trial systems available for SAP Cloud ALM.

Explore the Expert Portal of SAP Cloud ALM


  1. Open the Expert Portal and review the End to End Implementation Process Demos.

    1. Open the Expert Portal using the link and review the End to End Implementation Process Demos.

Tools in Project Management

Tools and Content: Project Management

Tools and ContentPurpose


SAP Cloud ALM is an Application Lifecycle Management (ALM) offering of SAP for customers that use only (or at least predominantly) cloud solutions from SAP, and do not want to deploy their own ALM platform on-premise to manage them.

SAP Cloud Appliance Library

SAP Cloud Appliance Library offers a quick and easy way to consume the latest SAP solutions in the cloud, such as SAP S/4HANA.

SAP Solution Manager - Cross Topics (only for customers still using SAP Solution Manager)

Content Activation, SAP Solution Manager Setup, SAP Premium Engagement Delivery, Project and Operations Analytics, KPI Catalog.

SAP Solution Manager - Focused Build ​(only for customers still using SAP Solution Manager)

Focused Build is a ready-to-run and integrated, tool-supported methodology to manage requirements and software development in large, agile projects.

SAP Solution Manager - Project Management​ (only for customers still using SAP Solution Manager)

Program and Portfolio Management, Task Management, Scope and Timeline, Requirements Management, Resources, Efforts and Costs Management.

SAP Activate Roadmap Viewer

  1. What is the SAP Activate Roadmap Viewer?

    The SAP Activate Roadmap Viewer provides access to Solution Implementation Roadmaps, which represent a structured approach to the software implementation process.

    Activities are split into distinct phases, with deliverables and tasks that help project teams to betterplan, execute, and manage their implementation project.

  2. SAP Solution Implementation Roadmaps aim to assist by providing implementation Project Teams with recommended lists of the following:

    • Deliverables (the 'what') in each phase.
    • A process description in the form of details and tasks (the 'how').
    • Accelerators (such as templates, examples, guides, and web links) to be used in the Project Library.


Application and Configuration Workstream

To facilitate the work of configuration, development, and security implementation, SAP provides several tools and resources. One of the most important examples is the SAP Fiori Library. When using SAP Best Practices, you will find a relation between the app and the scope item codes.

In the SAP Fiori Library, you will find information about which Fiori apps are available for each product, which are the prerequisites (addons, patch level), how to install and configure the app, which security roles are provided, if it's possible to extend the app, features, and look preview. If you have the right access to the SAP support platform, you can access SAP Maintenance Planner to identify the upgrade or update the path that you will allow to bring your current solution to the required software levels. SAP Fiori apps library also allows the identification of related apps that can be relevant for end users.

One of the advantages of the SAP Fiori Apps Library, is, that it allows the identification of related apps that can be relevant for end users.

Explore Content in SAP Fiori Apps Reference Library


Explore the content available in SAP Fiori Apps Reference Library (

Access the details for SAP Fiori Apps Reference Library ( for the Cash Flow Analyzer tab. Browse through the tabs Product Features, Implementation, Related Apps.


  1. Explore the content available for the Cash Flow Analyzer in the SAP Fiori Apps Reference Library.

    1. Explore the content available in the SAP Fiori Apps Reference Library,

    2. Access the details for the Cash Flow Analyzer tab,'F2332')/S24OP

    3. Browse through the tabs Product Features, Implementation, and Related Apps.

SAP Signavio Process Navigator

With SAP Best Practices, SAP delivers standardized business practices, implementation methods, and accelerators for a wide range of SAP software.

The prepackaged solutions are published in SAP Signavio Process Navigator as packages with assets covering solution design, configuration, and software and delivery requirements.


List of Modular Processes and Scope Items



Roles: Analytics

Analytics ArchitectCustomer IT
  • Definition of Analytics Strategy in alignment with SAP Implementation Roadmap and company IT strategy
  • Ensure compliance of Implementation Partner work with the strategy and development standards for analytical and reporting applications
Analytics ConsultantImplementation Partner, Customer IT
  • Design of high-performance and high-quality data sources and data processing mechanisms in the selected applications
  • Design of dashboards and data use case (Stories) for efficient data consumption
  • Competent shall include scope of courses relevant for Analytics and Reporting solutions being implemented 

Concepts of Customer Team Enablement

Customer Team Enablement Options

Customer Team Enablement Options

Enablement OptionComment
Partner-led EducationImplementation Partner may propose own educational services based on partner owned solutions or partner experience specific for the customers’ industry. Partner uses self-develop education materials and systems.
Self-educationOverviews for IT experts provided on SAP Learning Hub, as well as information and Accelerators in SAP Signavio Process Navigator and SAP Activate Roadmap Viewer.
SAP Education - Public WorkshopsFull spectrum of courses from SAP S/4HANA overview through fundamentals to in-depth trainings on a specific functional or technical topic. Public means that workshops are not customer-specific and are open for public registration.
SAP Education - Customer-specific WorkshopsCourses shaped to meet individual customer needs. Use content from public or customer courses developed by trainers. Location may be SAP Education Center or Customer premises.

Customer Team Enablement Options (Continued)

Customer BusinessFor SAP S/4HANA implementations, the minimum recommended level for efficient project work is to pass SAP S/4HANA overview, Integrated Business Processes overview, and Line of Business overview courses. Project-specific training on Solution Validation and fit-to-standard workshop approaches is recommended.
Customer ITOften, customer IT roles are coming from legacy technology platforms and business solutions, so it is important to understand ideology of integrated business processes in SAP S/4HANA together with technologies used for in Technical Architecture and Infrastructure, Extensibility, Integration, and Operations and Support Workstreams.

Customer Team Enablement Areas

  • Major enablement areas for the customer team are:

    • Solution Expertise

    • Technical Expertise

    • Project Management

  • All customer team members shall have overview training on SAP Activate.

  • Prior to Solution Validation workshops, guidelines should be developed and there should be a training on Solution Validation Guidelines.

  • Solution and Technical Expertise training shall be part of customer team training plan, and delivered prior to Solution Validation.

  • Workstream specific knowledge also transferred to customer team members during information and design thinking workshops within relevant workstreams.

  • Register of Project Procedures shall be drawn from the project management plan, and the customer team shall be trained on these standards (and tools, including Solution Manager) as soon as standards are developed and tools are set up.

Learning Needs Analysis

Concepts of Solution Adoption

Solution Adoption Substreams

End User TrainingEnsure end users are ready to use new solution accordingly.Starts with end user training strategy development and spans until end user training before go-live in the Deploy phase. Also, training program for new end users who will join company after SAP S/4HANA go-live should be developed.
Value ManagementEnsure all decisions are made based on Business Value and Business Value expected by stakeholders is achieved.Starts with Business Transformation Reviews to set basis for Business Value expectations and throughout the project Value Audits are conducted to ensure Business Value is in focus of the project team.
Organization Change ManagementEnsure all stakeholders are identified and involved into project and they accept changes caused by the project.All stakeholders’ interests should be taken into account and managed throughout the project to ensure that new solution will be adopted by the organization. Changes in organization structure should be aligned with stakeholders and running business transformation initiatives.

Train the Trainer (TtT)

When a new solution is implemented, new learning needs will arise as impacted users will need to learn new ways to perform their tasks.

One critical task is the related to Organizational Change Management (OCM).

The purpose is to conduct all relevant Organizational Change Management (OCM) analysis (change impact analysis, communication needs and channel analysis, learning needs analysis, and stakeholder analysis) to develop and plan OCM activities for what, when, and who. This supports an efficient and effective OCM delivery impacting change readiness and end user adoption.

The next step is to identify and nominate change agents as the ambassadors to support the digital transformation.

SAP Activate Methodology for SAP SuccessFactors

When you look into the roadmap for SAP SuccessFactors and check the solution adoption workstream, it seems that the solution adoption is not much present in the early phases of the project. That is not correct. The emphasis provided the overview diagrams sets focus on some activities but once you explore the content (tasks and accelerators), you will notice that activities will take place. OCM impact analysis takes place in the Explore phase like for other roadmaps.

Access the SAP Activate Roadmap Viewer to Look for Change Impact Analysis



  1. Access the SAP Activate Roadmap Viewer and look for accelerators that help you conduct your activities for change impact analysis.

    1. Access the SAP Activate Roadmap Viewer and use the search field to look for change impact analysis. If you do not find meaningful results, check the following: or use this

Concepts of Extensibility

Concepts of Testing

Any project requires some sort of testing. The typical sequence will involve:

  • Unit testing

  • Business process testing, also called string testing

  • Integration testing

  • Data conversion testing

  • User acceptance testing

Testing Types

TypeObjectiveConducted By
Unit TestTo confirm that individual transactions and RICEFW developments have been correctly configured.Implementation Partner
String TestValidate and verify the system components against Solution Documentation.Customer IT
Integration TestTo validate that all software module dependencies are functionally correct, and that data integrity is maintained between separate modules for the entire solution. Main focus: End to end business processes.Customer IT
User Acceptance TestTo check if the system can support day-to-day business and user scenarios and ensure the system is sufficient and correct for business usage.Customer Business
Regression TestConfirm that new functionality not causing defects in existing functionality.Customer IT
Security TestConfirm roles and authorizations are sufficient to execute business process steps according to Solution Documentation.Customer IT
Performance TestTo measure the quality attributes of the system, such as scalability, reliability, and resource usage. to make informed decisions related to the system.Customer IT
Technical Infrastructure TestConfirm that high availability, disaster recovery, backup and restore, infrastructure security areas compliant with technical design document.Customer IT

The test planning starts early in the Explore phase and it will take place during the Realize phase.

The testing starts from an atomic approach, like unit testing or even to unit integration testing until it starts to address end to end processes. Other scope elements can be included, like security testing or performance testing.

Not all types of tests are always relevant when you build something new. There’s no point on conducting regression testing. When you change something that is already built, regression will allow you to identify any possible side-effects.

Find out More About the Test Workstream


  1. Open the SAP Activate Roadmap Viewer and look at testing strategy definition tasks.

    1. Open the SAP Activate Roadmap Viewer using and look at the testing strategy definition task.

  2. Open the SAP Activate Roadmap Viewer and get acquainted with the characteristics of different types of testing, like regression testing.

    1. Open the SAP Activate Roadmap Viewer using and get acquainted with the characteristics of different types of testing, like regression testing.


Concepts of Operations and Support

Even if you opt for a cloud solution, certain aspects of operations will remain your responsibility.

Customer Center of Expertise (CCoE) is an organizational model that serves as collaboration hub across IT and LoBs. The mission of the CCoE is to provide transparency and efficiency of SAP implementation, innovation, operation, and quality of business processes and systems. CCoE centrally drives continuous improvement and continuous innovation.

  • Hypercare period or stabilization, is a period after go-live within the Deploy phase. Its purpose is to ensure that all critical issues, which occurred during cutover or after users started working with the system, are resolved urgently to support business processes operations.

  • The most common issues within hypercare period are:

    • Urgent authorization changes, and

    • Questions on using functionality.

  • Most common approaches to hypercare period:

    • Temporary procedure for emergency authorizations provisioning (artifact 'Project Procedure - User Management for Go-Live').

    • Distribution of Application Consultants among offices.

    • Setup of dedicated space where users may come and perform operations with Application Consultants assistance.

Concepts of Data Management

Data Management Workstream consists of three substreams:

  1. Data Migration: deals with migrating legacy data (master data as well as very limited transactional data) into target SAP S/4HANA system.

  2. Data Volume Management: aims at keeping required system performance level and optimizing TCO by storing the right (mostly transactional) data in the right place.

  3. Master Data Management: target is high data quality and data unification and its efficient management within business solutions landscape.

DVM concept is used for (1) decreasing volumes of migrated data, for example, by implementing DVM measures in source SAP ERP system before System Conversion and (2) avoiding explosive data growth in the SAP S/4HANA system.

The data volume management (DVM) service goes into:

  • Data avoidance and when and how to use this for *YOUR* system
  • What data can be summarized on *YOUR* system
  • What data can be deleted or truncated, and is unnecessary for *YOUR* system
  • What archiving objects exist today, what will exist in SAP S/4HANA, and where archiving will exist

Concepts of Technical Architecture and Infrastructure

This workstream can play quite different roles, some will be common across different roadmaps. In any project during the Realize phase, you will be performing changes to the existing security objects, for example, business roles based on the requirements collected in the Explore phase. When you adopt a new solution or convert from a earlier version, changing security definitions that translate into what a user is authorized to do or not are always to be expected.

As systems have become more integrated and hybrid scenarios more common, SAP has developed new solutions that can handle the needs of cloud and on-premise implementations. Examples of those solutions are:

  • SAP Cloud ALM

  • SAP Identity Services

  • Technical Architecture and Infrastructure for SAP Implementation is first captured during Discover phase and contains points of view on:

    • Data center strategy

    • Scalability, availability, and capacity (hardware sizing) requirements

    • SAP recommendations on system landscapes for a specific solution

  • Based on initial point of view, initial hardware specifications are developed for purchasing hardware. Because detailed requirements and solution design are discussed during Explore phase. The sizing should only be relevant for Private Cloud Edition as it is the only on-premise approach offered.

  • During the Realize phase, a performance test is conducted to confirm that the solution is ready for productive load. Corrections in hardware might be required.

Log in to track your progress & complete quizzes