 | ||
A change request is a document containing a call for an adjustment of a system; it is of great importance in the change management process.
A change request is declarative, i.e. it states what needs to be accomplished, but leaves out how the change should be carried out. Important elements of a change request are an ID, the customer (ID), the deadline (if applicable), an indication whether the change is required or optional, the change type (often chosen from a domain-specific ontology) and a change abstract, which is a piece of narrative (Keller, 2005). An example of a change request can be found in Figure 1 on the right.
Change requests typically originate from one of five sources:
- problem reports that identify bugs that must be fixed, which forms the most common source
- system enhancement requests from users
- events in the development of other systems
- changes in underlying structure and or standards (e.g. in software development this could be a new operating system)
- demands from senior management (Dennis, Wixom & Tegarden, 2002).
Additionally, in Project Management, change requests may also originate from an unclear understanding of the goals and the objectives of the project.
Change requests have many different names, which essentially describe the same concept: