Register now or log in to join your professional community.
Situation: Client has asked for website to create event creation for concerts. The development team understands the requirement as a real time ticket vending system. They also started developing a website that allows users to create events/concerts which others can view lively or go to event. All the solutions were top notch and clients were happy. When almost all the parts of the system were ready and being tested separately for quality breaks, the team understood that the client wanted a game based environment and allowed users to create events/concerts that could play their favorite music and more participation from viewers will get more credits for the game. So all the events and happenings in events are all imaginary. When they let the clients know about this, clients were unhappy. Development team also showed the scope documents and other documents they signed as a contract. But the client is now claiming that it was too technical for them to understand and it was not what they asked for. What would you do in this situation? What would your actions would be?
I would first review the requirements and scope of the project. Next, I would then follow up with the client to identify the gaps and document them in sufficient detail. Based on our discussion, I would devise a plan that included milestones to allow the client to review progress. A formal acceptance from the client would be required to proceed. Once project work has commenced, monitoring and controls are implemented to prevent any changes in the scope baseline.
