A first-time project manager wanted to have a “perfect project.” This manager informed the customer that this project would not accept change requests of any kind and that the scope would need to be defined precisely at the very start of the project. The customer agreed to this request. What would your comment on this situation be?

The is a good example of how the project management team can decide what is and what is not necessary for the project. Not allowing changes is a good way of ensuring that the project meets requirements as detailed in the project scope.

This is unrealistic and impractical. Change is inevitable and rather than look at a 'no change' project, it would be more in the project interests to plan for a robust change control process.

This indicates that the project manager is very aggressive and is likely to take the project to successful completion. Since he has announced the 'no change requests' policy, the customer manager can no longer request changes.

This is unrealistic and impractical. The project manager should not have announced his intentions to the customer. He should have had an unofficial policy of rejecting all change requests.