One of the most common problems a Project Manager will face with the client is with the project's scope. It defines what will and will not be done. In essence, the project's scope defines the expectat

One of the most common problems a Project Manager will face with the client is with the project's scope. It defines what will and will not be done. In essence, the project's scope defines the expectations of the client/customer and the expectations of the project manager. Far too often, those expectations will differ, and that becomes the friction between the parties. What is 'scope creep'? If the client/customer is disappointed, they will take their business elsewhere in the future or, the project manager will seek out other clients/customers or project opportunities.

How can the expectations between the parties be designed so that there is a minimal amount of friction between the parties? Research real-life scope and 'scope creep' problems; and, possibly, give some of your real-life examples. How would you, as a project manager, avoid scope problems/disputes and 'scope creep'?