Designing the To-Be Solution

Objectives

After completing this lesson, you will be able to:

  • Describe how to capture requirements from a fit-to-standard workshop

Recommendations for Designing the To-Be Solution

The implementation project at Dreams without Limits has started. As it now comes to the design of the Hire to Retire process, Paula meets Alexander again.

Designing the To-Be Solution

Alexander points out that the main tasks during the Design step are to create the project in SAP Cloud ALM, to onboard the team members and to manage the fit-to-standard workshops with SAP Best Practice content.

After this meeting, she hands over the design part to Peter Process. Peter needs to work closely together with Carl Consultant from the implementation partner Implement HXM!.

Introduction to Process Management

Peter is happy, because he has learned in his previous meeting with Carl that SAP Cloud ALM already contains the Best Practices from SAP Activate. However, as Dreams without Limits may want to adapt the SAP standard process for Hire to Retire according to their needs, he asks Carl how these changes can be captured, documented, and tracked.

See the following animation to get Carl’s answer:

Process Management

The Fit-to-Standard Workshop and Capturing Delta Requirements

Peter has learned that the fit-to-standard workshop plays a central role during the design of the to-be solution. But what exactly happens during this workshop?

What is Fit-to-Standard?

The SAP standard processes allow for an efficient approach to validating the fit of the customer requirements to the SAP standard solution. The fit-to-standard workshops are organized around the functional areas of the solution and are used to explore the functionality, to show how the solution can meet business requirements, and to enable business process experts to execute processes. Delta requirements are identified, discussed, and then added to the backlog. The fit-to-standard analysis uses an iterative approach to ensure that integrated dependencies are addressed.

During the workshops, configuration changes (requirements) are determined and cataloged as outputs of the fit-to-standard process and are used as inputs for the Solution Configuration process in the next phase.

In each workshop, the following process takes place:

  1. Review the standard processes.
  2. Demonstrate the business processes and concepts.
  3. Discuss how the processes fit with customer requirements.
  4. Identify delta requirements (such as analytics, output management, integration or extensibility).
  5. Identify the required configuration to fulfill the requirements.
  6. Enable the customer on the execution of processes.

Finally, Peter has another question. He wants to know how the delta requirements or additional information are captured:

Determining the Project Scope – Capture Requirements

Carl explains the difference between requirements and notes:

  • A requirement details delta requirements that the solution variant should fulfill to comply with the customer’s expectations. Requirements are actionable and (after approval) turned into tasks to facilitate the fulfillment. Business Process Experts such as Peter can specify the appropriate workstream (such as Integration or Analytics) to work on the requirement. The customer can approve requirements and decide if a user story or a project task is then generated automatically.
  • Notes are used to document any additional knowledge or insight about a business process that is useful to remember. They are timeless and part of the process documentation.

Both requirements and notes can be created from the process diagrams using call-out buttons and from the side panel by using the Create button.

Note

In addition, you can capture requirements manually in the "Requirements" app or via API or upload from Excel.

Determining the Scope

Capturing Requirements

Log in to track your progress & complete quizzes