Task: Submit Change Request









var backPath = './../../';
var imgPath = './../../images/';
var nodeInfo=[{view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_LWLSQDIEEdqwaNnSEheSAg", "_EzUssACVEdqrKcHWz1HoWw", "{8570B861-6749-421E-A469-38D369342D39}", "{1393CA8E-5CA4-4494-93FE-587F51931896}"]}, {view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_LWLSQDIEEdqwaNnSEheSAg", "_hsuoEDIFEdqwaNnSEheSAg", "{1393CA8E-5CA4-4494-93FE-587F51931896}"]}, {view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_4U33kAILEdq-_NKqZM1EhA", "_nB0hwAITEdqu-LkyOdB8SQ", "_yeA1xNnmEdmO6L4XMImrsA", "{1393CA8E-5CA4-4494-93FE-587F51931896}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_f6_YwN7DEdmsEI4YDGX2ag", "_EzUssACVEdqrKcHWz1HoWw", "{8570B861-6749-421E-A469-38D369342D39}", "{1393CA8E-5CA4-4494-93FE-587F51931896}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_kC0pcN7GEdm8G6yT7-Wdqw", "_yeA1xNnmEdmO6L4XMImrsA", "{1393CA8E-5CA4-4494-93FE-587F51931896}"]}];
contentPage.preload(imgPath, backPath, nodeInfo, '', true, false, false);










Task: Submit Change Request















This task describes how to create a Change Request.


Disciplines: Configuration & Change Management






Purpose



This task logs a requested change. Change Requests may include requests for new features, enhancements, corrections, changed requirements, and so on. Any role may submit a change request as part of any task throughout the project lifecycle.



Relationships



RolesPrimary Performer:



Any Role


Additional Performers:



InputsMandatory:


None

Optional:



Iteration Plan






Outputs


Change Request






Process Usage


Configuration & Change Management
 > 
Manage Change Requests
 > 
Submit Change Request






Steps




Complete Change Request Form



The Change Request Form is a formally submitted work product that is used to track all requests throughout the project lifecycle This includes new features, enhancement requests, defects, changed requirements, etc. All change history will be maintained with the CR, including all state changes along with dates and reasons for the change. This information will be available for any repeat reviews and for final closing. An example Change Request Form is provided in Work Product: Change Requests.



Submit the Change Request



Once the CR is completed, it should be submitted through the proper channels to assure compliance with the established Change Request Management Process. Any stakeholder on the project can submit a Change Request (CR). The CR is logged into the CR Tracking System (e.g., ClearQuest) and is placed into the CCB Review Queue, by setting the CR state to Submitted. Typical states that a Change Request may pass through are shown in Change Request Management.







More Information



Tool Mentors


Submitting Change Requests Using Rational ClearQuest








©  Copyright IBM Corp. 1987, 2006.  All Rights Reserved.







contentPage.onload();