Define acceptable gaps and workarounds
The standard product is a great product, but obviously it cannot contain all the functionalities necessary for the company. It is necessary to try to adapt to it or use workarounds to manage what may seem unmanageable.
In addition to the work of consultants, already seen in the previous chapter, the customer must play their part in trying to adapt as much as possible to the standard and accept any unmanageable gaps that can be bypassed by workarounds proposed by the consultant. The customer (the key user of the process in general) must always be the sponsor of the project and of the product.
If, instead, new gaps/requirements emerge that cannot be managed through workarounds (during the project or after the go-live date), it is necessary to classify them so as not to alter the course of the project, under an example of classification. For example, we can classify the new requirements/gaps that are detected in this way:
- Need to start
- Need after starting
- Nice...
