The Purpose of life is to go toward the freedom and drop all the fears of life. - Upanishdas
About Me
44% of pm use no software, even though PWC found that the use of commercially available PM software increases performance and satisfaction. Follow Tweet

Metrics: Leading Causes of Failed Agile Project Follow Tweet

Control Scope

Control Scope


My Message!

Click “X” to close.

Control scope is monitoring and controlling process. In any project especially large, complex, long duration, distributed team project it is possible that changes will go out of the control. If project management team is not able to manage and control the changes then no matter how good your project resources are you will never be able to complete the project successfully. This process is about managing and controlling all the scope and requirement changes. PMBOK’s focus is to emphasize that commit your deliverables and deliver whatever has been committed. It does not encourages project managers to deliver anything more or less than committed. Anything which is not committed if you are trying to deliver it is called gold-plating. Anything which is committed and you do not deliver it is called over committed or under delivery. Project managers must know how many change requests were rejected and why, how many change requests were accepted and why? What is over requirement stability and delivery status of the project. This process helps you in achieving all this.

Being a monitoring and controlling process important outputs of this process are metrics related to scope and requirements. If any course correction is required in the project then that can lead to raising change request.
Previous Process Next Process

Control Scope:Process Table

Want to add something?

Loading Facebook Comments ...

Leave a Reply

Your email address will not be published. Required fields are marked *


Loading Disqus Comments ...