A project change is any change to what a project is delivering or how it will be delivered. Generally speaking, all changes have an impact on a project such that they influence project complexity and scope. The following are common examples of project change.
Architecture
Assumptions
Change to organizations
Change to target environments – change to what you are changing
Constraints
Definitions
Deliverables
Design
Interpretations of requirements
Locations
New administrative processes
New overhead such as meetings that must be attended
New reports and communications
New risks
New stakeholders or sponsors
Non-functional requirements
Partners
Project methodology
Quality standards
Regulations and compliance
Requirements
Resources
Technologies
Tools
Project change can extend far beyond what is controlled by a change control process and change requests. This phenomenon is known as scope creep.People tend to have the mindset that project change relates solely to requirements. For example, a change in the time constraints of a project is not viewed as having any impact on budget or complexity. This is incorrect as delivering something faster requires more resources and thus more coordination overhead. Delivering something slower may result in idle resources that impact budget.
Cookies help us deliver our services. You have choices regarding these cookies. Please visit our privacy policy, cookie policy and consent tool to learn more.
Copyright 2002-2026 Simplicable. All rights reserved. This material may not be published, broadcast, rewritten, redistributed or translated. Report violations here.