Managing the change requests in project efficient way

Success Problem

I am managing frequent changes in project scope - how to do this correctly? Is it possible to avoid frequent change requests in the project as it requires extra work to prepare a CR analysis, effort estimation, acceptance criteria, and project steering group approval?


The unclear or only high-level described scope for the project often results in unaccepted deliverables, not keeping the project schedule, and cost overflow.


Managing a change in project scope starts with defining project acceptance criteria. During the creation of project detail WBS, the project manager should not only define resources but as well assign to WBS milestones clear deliverables and acceptance criteria. If a discrepancy between the scope defined in the project contract and reality is detected during this planning phase, it's best to handle it as soon as possible. Follow the simple rule: the later the CR comes, the more it usually costs.



Forgot Password?

Don’t have account? Register here!

Please read the Terms of Use and Privacy Notice

User Agreement:
Check here to indicate that you have

We have sent an email with a confirmation link to your email address. In order to complete the registration, please click the confirmation link.

The link expires within the next 14 days.

Please check, whether the email is in the junk folder, since confirmation mails with backlinks are sometimes classified as spam.

Please press the button.
Save All Changes.