Klara Södra 1, 111 52 Stockholm

Contact us today - 98457 ACEPM (98457 22376)

Sudden changes in Requirements

Ajay Khana has around 5 years of experience in the IT industry He joined Wipro, 4 months back taking charge for a new project in utilities domain. The initial phase has passed smoothly with requirements clearly documented and projects slowly moving into development stage after finishing design. Arriving at the Hosur Road signal, he takes a left and enters Madivala office in his new Santro. Parking the car; he reaches for the lift and in moments he is in his cabin. The morning calm has energized and he starts to browse his mails with vigor and enthusiasm. He browses his mails and finds a mail from Jeff, his customer. The mail describes additional features to be incorporated in the system.

Panic engulfs his peace. The project has already entered the coding phase and activities are underway. If the changes are communicated then, team members may loose morale as their design efforts need to be revamped. If he rejects the changes, from an organizational perspective he would be guilty for loosing the client. Rattled out of his comfortable position he starts wondering what to do.
He can :

1. Call the customer and explain him that, this will not be possible. Provide him with statistics and clearly communicate that Wipro may even terminate the contract

2. Analyze the extra effort involved and give a separate proposal for incorporating the additional functionality. Increase the cost so that the customer thinks twice, before changing his requirements again.

3. Accept the situation as is and determine the impact of the changes. Quantify the impact in terms of features, effort, schedule and resources (manpower). Negotiate with the customer with data on hand and reduce the discomfort due to the changes and strike a new balance.

4. Accept the changes without any hesitations to impress the customer.

5. Any other option.