What if it rains before your crops have been harvested?
An unseasonal rain is a devastating phenomenon. And for the farmers like us, it’s a matter of trustworthiness. However, instead of crying, we will work out ways to overcome the loss.
Effects of Change in the project:
Resources:After the recognition of amendments, requirements were re-assembled and defined again. Clear communication was established including all the process heads along with us and the client provided us with the Requirements for development.
We, as the vendors added more back-end developers to match the project outcome. This left us unavailable for our other projects onboard. As our entire back-end development team was confined with this redevelopment of the auto-part quoting tool project, we couldn’t take up any new projects in hand.
Timeline: Changes were essential in the back-end, and not in the designing or front-end of the project. As the designing and front-end development occurred parallel, little change was required. We focused on the change while undergoing back-end development, and the timeline of the project was re-established.
“Rome was not built in a day”. Everything requires time to heal.
Co-operation: : It takes two to tango! This is definitely the prime and most essential remark to be addressed. Instead of rising conflict, problems or blaming each other, the client and our team, both understood the situation well and co-operated to help each other out in finding a solution to the occurred problem.
A mutual understanding between the two is indispensable. The Vendor and the Client must come on common grounds and support each other to solve the issue.
Like in this best enterprise app development case, we reevaluated projects and collaborated with the client departmental team heads and intervened the entire process. Similarly, though the client wanted early outputs, he was patient enough to wait for us to recompile the back-end, add the lacking features and re-test everything. Mutual consensus solves the issue.