A question for a future video: In large implementations, a common practice is to issue an RFP to the vendor. The document often includes hundreds of one or two-line requested features or functionalities. The vendor usually indicates availability in their system (yes/no/further development), however, very often the understanding of the features requested is minimal as it is based on a very short description. The whole process is very cumbersome and fuzzy as the vendor is unsure what exactly is requested and the customer gets mostly wrong information on what is available in the system. Is there a better way to perform this process?
A question for a future video: In large implementations, a common practice is to issue an RFP to the vendor. The document often includes hundreds of one or two-line requested features or functionalities. The vendor usually indicates availability in their system (yes/no/further development), however, very often the understanding of the features requested is minimal as it is based on a very short description. The whole process is very cumbersome and fuzzy as the vendor is unsure what exactly is requested and the customer gets mostly wrong information on what is available in the system. Is there a better way to perform this process?