Register now or log in to join your professional community.
note that this client has a similar system and is resisting the changes through adding requirements, while persuading the client with the pro's of the new system through integrating the fundamental requirements. Moreover these requirements were not mentioned in the scope of work (SOW)
Adding requirements or more feature to the scope is expected throughout the project despite all the efforts placed to control the project. The customer might request a change. In this case, the PM should assess the impact on this scope change and advise the customer of the returned impacts on other constrains. If yet insisting that this new requirement is necessary, PM should issue a change request to the project change board for the resulted changes on Time, Cost, Quality and other project management plans. project management plan and project documents are updated after the approval is obtained.
Considering these requirements were not part of the Scope of work and the requirement analysis and as you mentioned, that the project is in execution phase, i suggest that the Change management process to be initiated. As part of the changemanagement, the impact of the change need to be analysed in terms of cost and time and reverted back to the project board as well as the client and upon approval can be made part of the project scope.
