1 Years To Complete The Project?
What makes our stakeholders to have a decision for proprietary software buy-in? Literally, one stakeholder was eager to implement a “brand-new-cool” solution for automating a few of the business procedures that forced him to hire 3 more employees. That said, we have: the stakeholder X, the software product Y, which should put into action function Z. And lastly, the software product Y doesn’t include its sources in the delivery package. As you might have already guessed, this software had not been working properly after set up and we’re able to not integrate the info model as the software wasn’t suitable for some specific business cases. Let us take a look to the main of the problem.
The stakeholder knew that the merchandise cannot perform some functions, so the required customization was ordered. Next, after the contract was signed, we were testing our data integration procedures with every new version of the merchandise. And, we were receiving the new variations every 4-5 weeks, regularly, with some bugfixes. Nice. After about 2 years (!) of such integration process we’ve got to know, that by the time of agreement putting your signature on, there have been no customers who succeeded to integrate this product.
And, some customization reasoning was not working by this time around still. At this time the project is 3 years old almost. Lately we received the new version that was claimed to work accordingly to the ordered specification. As I view it at this time, the stakeholder’s perspective in …