Guideline: Review Change Request |
This guideline describes what to consider when you review a change request.
Relationships
Related Elements | Review Change Request
Main Description
Analyze the change request: Who issued the request? Do we understand the request? If not, get more information from the request Submitter. Does it apply to our product or responsibility? If not, inform the Submitter. Categorize the request (enhancement, defect, and so on). What is involved in implementing the request? Analyze what the impact will be on the existing artifacts. Are there additional artifacts that need to be created? The result of the analysis is a determination of the impact of the change on the existing requirements (a list of new or affected requirements), and of how much effort it will take to implement the change. Perform (or delegate) an overall impact assessment, and effort estimate including: System dependencies Technology, resources, and skill required Which artifacts are affected: requirement impact, design impact, implementation impact, and so on Is there sufficient basis to justify the request? Does the business case exist? Inform the appropriate decision maker and seek approval to perform the work. The results of the analysis may lead to a number of change requests for related artifacts within the system. The review of a change request may also result in one or more child change requests being created.
© Copyright IBM Corp. 1987, 2009. All Rights Reserved.