Solution validation - Workshop type A

The purpose of this workshop is to challenge changes to SAP standard functionality and determine whether there is a real need for enhancement or change that is affecting one or more business values. The result of the workshop is the list of Delta requirements and gaps.

The approach followed here is a top-down approach, where we start with an overall solution and then drill down to processes and functional details. The sequence of activities in this workshop can be jotted down as follows:

Workshop A: Sequence of activities

Once we have identified the gap and Delta requirements via workshop type A, then we can create an initial backlog with a Delta score prioritization before moving to workshop type B. Delta score prioritization is not a part of any of the two workshops, but it is a result of workshop A and input for workshop B. The business users prioritize the backlog depending on the sequence of features to be implemented. This will be used by the project team for the Delta design workshop and gives clarity on what they should focus on.

At the end of backlog prioritization, the Delta requirements and gaps are identified, ownership is decided, and associated SAP business processes are identified:

An example of initial product backlog

For premium engagement projects, SAP's Innovation Control Center (ICC) enables the project team to validate integration projects and prepare for smooth operations, enabling agile and continuous deployment of changes to the customer system. Project teams can submit gaps to the MCC for validation using transaction SMFG.