Review the business processes of the relevant solution with your customer. To what extent do the business processes fit the customer requirements. Mark the business processes that don't fit the customer needs as a gap. This usually results in questions to be answered and requirements to solve the gaps. You can use fit categories and gap categories to indicate the sort of fit or gap.
Name | Responsible | Description |
---|---|---|
Define fit and gap categories |
Business analyst |
You can define several fit categories or gap categories for your implementation project. When you verify processes and it fits or you find a gap, you can link the related fit/gap category to the business processes. Thus, indicating the sort of fit or gap for the business process. |
Run workshops to review business model |
Business analyst |
Review the business processes of the relevant solution with your customer. Do the business processes fit the customer needs? |
Verify processes |
Business analyst |
Verify the processes as described in the business process flow and mark them accordingly as Fit or Gap. One of these scenarios is applicable:
The steps explain how to mark a business process as a fit, without a fit category defined.
|
Publish process verification |
Business analyst |
You can publish a document with the result of the process verification of a solution. Only the business processes that are in scope are added to this document. Separate chapters are created for the business processes with gaps and the business processes that fit. You can configure the level of detail of the information that is added to the document. You can find and download the published document on the Business process file share workspace, on the Documents tab. |