Customer change requests during the ongoing project

The target specification developed together with the customer describes the functional requirements of the new development project.

With the release of the requirement specification in written form, this functional scope is frozen. This means that no further changes should be made after the release date, so that the defined project goal can be reached within the agreed time and cost framework.

Depending on the extent and complexity change requests of the customers during the ongoing project, if possible, should always be implemented in a follow-up project.

Generally, change requests of customers during the ongoing project always require a re-evaluation by a committee or a board – in a varying composition depending on the extent of the change.

 In addition to the responsible project manager such a committee may consist of:

- the complete executive board
- the CEO
- the head of “Development“
- the head “Sales & Marketing“
- department managers affected by the project
- team leaders affected by the project
- staff members involved in the project (resources)

 Criteria for arranging such a committee may be:

- departments affected by the rescheduling
- projects affected by the rescheduling (also indirectly affected by shiftings)
- human competences and responsibilities (resource manager)
- special competences and responsibilities (specialists)

In case the committee cannot implement a customer‘s change request at present, because it would not only blow the affected project’s schedule but also that of indirectly affected projects or no suitable resources are available, it should be intended to realize the changes in a follow-up project.

In case the implementation of the customer’s change request is approved by the committee, the planning is updated in line with the change management and, as the case may be, deadlines (also of other projects) are postponed, customers are informed, target specifications are updated, etc.

 
Don’t miss the previous 11 parts from this series:
Part I (https://mobacommunity.com/blogs/entry/The-MOBA-Project-Management-Part-1)
Part II (https://mobacommunity.com/blogs/entry/The-MOBA-Project-Management-Part-2)
Part III (https://mobacommunity.com/blogs/entry/The-MOBA-Project-Management-Part-3)
Part IV (https://mobacommunity.com/blogs/entry/The-MOBA-Project-Management-Part-4)
Part V (https://mobacommunity.com/blogs/entry/The-MOBA-Project-Management-Part-5)
Part VI (https://mobacommunity.com/blogs/entry/The-MOBA-Project-Management-Part-6)
Part VII (https://mobacommunity.com/blogs/entry/The-MOBA-Project-Management-Part-7)
Part VIII (https://mobacommunity.com/blogs/entry/The-MOBA-Project-Management-Part-8)
Part IX (https://mobacommunity.com/blogs/entry/The-MOBA-Project-Management-Part-9)
Part X (https://mobacommunity.com/blogs/entry/The-MOBA-Project-Management-Part-10)
Part XI (https://mobacommunity.com/blogs/entry/The-MOBA-Project-Management-Part-11)
Part XI (https://mobacommunity.com/blogs/entry/The-MOBA-Project-Management-Part-12)

To be continued…