Fit/gap analysis

The main objective of the fit/gap analysis is to identify any capture Delta business requirement and gaps, which might not have been captured in the preactivated or preassembled solution (sandbox). At the end of the analysis, it is expected that the team has finalized and gotten the approval for scope baseline to proceed into the realize phase.

This ensures that implementation meets customer's business needs and the customer's solution is aligned to SAP standard processes. It also provides an opportunity to relook and discuss the solution design, prioritized Delta requirements, and gaps. A good gap analysis reduces the need for rework during the realize phase. With fit/gap analysis, the purpose is also to validate the predefined scenarios, processes, and enhancements, and identify potential gaps between the delivered product and customer requirements. The deliverable only captures requirements for gaps. It follows an iterative approach to the existing documentation and models can be altered; changes should be marked and documented in the Solution Manager:

In the case of projects deployed on cloud, this activity is called Fit-to-Standard. Here, the focus is to make sure that there is an ability to absorb the quarterly innovations that are provided in the cloud. For an on-premise project, we do two workshops: workshop type-A for solution validation and workshop type-B for Delta solution design. Let's take a deeper look at these workshops.

Let's do a deep dive into fit/gap analysis—on-premise. The following content is specific to on-premise as cloud does not need it.