This article is part of an Essential Guide, our editor-selected collection of our best articles, videos and other content on this topic. Explore more in this guide:
4. - ITSM and ITIL: Terms to know: Read more in this section
Explore other sections in this guide:
- 1. - ITSM, ITIL and Lean: So happy together
- 2. - IT services management advice, straight from the pros
- 3. - ITSM: Addressing the chokeholds
In project management, a change request often arises when the client wants an addition or alteration to the agreed-upon deliverables for a project. Such a change may involve an additional feature or customization or an extension of service, among other things. Because change requests are beyond the scope of the agreement, they generally mean that the client will have to pay for the extra resources required to satisfy them.
One of the more challenging aspects of change management is ensuring that all details are sufficiently explicated and that all parties are in agreement as to what is expected. Explicit and detailed documentation makes it easier to identify when a change request must be submitted.
Change requests can also originate internally. Internal change requests can involve a wide variety of actions including patching and software and hardware upgrades.
Once a change request has been made, the process of change control should be undertaken to make sure that the request is satisfied efficiently and without unnecessary use of resources.