3. What is it ?
Possible reasons .
Preventing it .
Dealing with it .
3
4. Scope creep is defined as adding features
and functionality (project scope) without
addressing the effects on time, costs, and
resources, or without customer approval.
(PMBOK)
4
5. Poor implementation of change control.
Incomplete gathering of requirements before
project execution begins.
Insufficient involvement of critical stakeholders
(including customer)
Lack of support from executive sponsor and
enforcement power in project manager
Weak project manager
5
6. Commit enough time to requirements-gathering.
Giving a hand might cost you your arm.
Once a schedule has been created, assign resources
and determine your critical path using a PERT Chart or
Work Breakdown Structure ( pay attention to changes in
the critical path )
6
7. Shed the “Customer is Always Right” mentality.
Understand your priorities and the priorities of the project
drivers
Define your deliverables and have them approved by the
project drivers
Accept that scope creep will happen and prepare for it (
change request forms … etc ) .
7
8. Differentiate between change request and
GAP
Study any change based on its effects on
Scope , Cost ( direct and indirect ) , time and
quality . Have a clear approval role by
steering committee .
Example of change request form
8
10. Example : SAP ERP implementation.
How to make sure change is required
How to manage change …
Presentation title - Place and Country -
Date Month Day Year
10
11. When clear picture is not available
The methodology of project management
should be changed
Agile project management PMI-ACP
Presentation title - Place and Country -
Date Month Day Year
11
12. You can not stop changes
You can Control changes
Presentation title - Place and Country -
Date Month Day Year
12