Gap solution design workshop overview
The following sections cover the top-level aspects of the gap solution design and provide a sampling of the types of questions that are covered in each section.
Top gaps
The Top gaps section is intended to provide an overview for the primary critical gaps that the team has identified and get an understanding of the proposed solutions to fill those gaps, including the related business processes that those solutions will be supporting.
Reviewing the high-level details on each proposed solution and potential complexities that are involved will help provide the necessary context for having in-depth discussions about each gap solution in the later stages of the workshop.
This stage asks for you to provide the following information:
Short description of the gap
Business processes that the gap solution will support
Where the gap exists and whether it's a standard gap in the platform or a gap in the ISV solution
Solution type (custom extension, independent software vendor (ISV), and so on)
Description of the proposed solution to fill that gap
Indication of whether a proof of concept of the proposed solution has been completed or not
The level of effort for the proposed solution
Type of business impact that needs to be considered for this gap
The level of risk that is associated with the proposed solution
Review of each gap and solution
The next section of workshop explains each gap that was highlighted in the top gaps section. Having comprehensive discussions on each gap will provide you with an opportunity to gain clarity about business requirements and the proposed solution. This review will also help you determine if you're taking the correct approach or if alternative approaches are available that might have less risk or align better with the product roadmap.
This unit focuses on answering questions such as:
What are the business requirements that need to be met with the gap solution?
What's the business process or processes that the solution will support?
What's the approach to fill this gap? What are the solution details?
Do certain risks need to be considered with this approach?
Do dependencies exist on other solution components?
Do performance impacts need to be considered?
Do storage impacts need to be considered?
Does the solution add complexity to the business process?
What other solutions have been considered, if any?
You'll go through these questions for each gap that the team has identified for review. This process will help ease the conversations that are necessary to assess each gap solution and determine the best approach.