It'll be every project manager's wish to not to have to deal with scope creep issues in his / her projects. However, still there seems to be no tool or technique available to entirely avoid scope creeps in any project across the seas. Even the PMBOK(r)Guide-5th ed has not addressed this issue to the depth it should have been. We all know that uncontrolled scope change is scope creep.
PMBOK Guide Cl 5.1 Plan Scope Management. .. last sentence says ... "This plan ( scope management plan) HELPS REDUCE the risk of project scope creep." Note here the word REDUCE, not AVOID. Can we say no document / plan can AVOID scope creep entirely.? A well developed Scope Management Plan can only help REDUCE scope creep.
IMO, in any project, SOME scope creep is UNAVOIDABLE as 100% se can never be captured or documented during tender / bidding / contract-award stage. Even in well defined projects, minor changes/additional works will creep in without proper change order (CO) and this is to be handled carefully as it is culturally sensitive issue.
Hence, it''s better to identify it as potential risk and provide some contingency reserve (CR) for it at project manager level. The management also should anticipate some unknown-unknowns in the form of scope creeps from Clients and manage such risks through Management Reserves (MR) for smooth execution of project and enhanced customer satisfaction. Or,
Is scope creep an unavoidable cultural issue across the world? Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
You have to undefstand this: If you control the changes then there is not chances,for,scope,creep. Thats all from my side. To continue im this post do not add value,for me. Saving Changes...
Anonymous
I would like to highlight on the essentials required to control scope creep. Very critical fact here is to clearly define the in scope and out of scope activities of project. This would rather reduce the load up to 50%. Plan, assess and implement changes by adding contingency. You can read more about scope creep here: http://bit.ly/2cyXHC6 Saving Changes...
Point number 1:
The customer asking for something not covered in the scope and providing nothing in return (cost, time or any other resource) can be a cultural issue or different interpretation of contract between the parties (meaning the contract is ambiguous).
Point number 2:
How the project manager and the team respond to this situation is what defines if it is a scope creep or not?
The team has to first realize what the customer is asking for is part of the scope or not. If the team is performing the extra work without realizing it is out of the agreed scope, then the scope creep has occurred. If it is not part of the scope, the team must follow change control process. Then there can be 2 scenarios.
Scenario 1: The customer is ready to provide the change request. In this case there is no issue; the team follows the change control process.
Scenario 2: When the customer is not providing a CR for reasons mentioned in point number 1, then the PM has to decide if the matter has to be pursued as per the provisions in the contract or accept the request from customer without exploring the contractual options.
If the PM decides to accept the out of scope request from customer, then an internal CR has to be created to follow the change control process. The PM has to justify his decision to accept in the Change Control Board to get the CR approved/rejected. The justification could be customer satisfaction or part of some other negotiation strategy. The impact on cost, time or any other resource has to be provided from one of the contingencies.
In summary, customer asking for free “anything” could be a cultural issue or contract interpretation. The PM & team recognizing whether the request is part of scope or not and acting as per the process will avoid scope creep.
I hope you find my answer helpful. Saving Changes...
Are we really arguing that scope creep is cultural, incredible! I've seen that this is an old post that is open again. @Sergio, I should said that most of us will be in your side.
Cultural is go to the supermarket and ask for a free sample of a fruit, it is common in USA and in most European countries would take you as a crazy customer.
I think that all of IT Project managers in this community, we have heard expressions like this " this modification will take only 5 minutes , could do it for free?," that is where the figure of the project manager play to follow defined processes and follow the CCB .
@Visswanathan my comments
Point 1, clients, account managers, always request free stuff, our job is always said NO and follow the procedure. No cultural point here. Also you’ve also talked about different interpretation of the contract. Then as a project manager you should ask to the procurement manager or in certain point to PMO or take a lawyer (Attorney)
Point 2. All your notes have no sense for me, sorry. Team performing extra job it means the project was not planned correctly.
As project managers we have to ensure always scenario 1, it means follow the procedure. Saving Changes...
