Design Change Request Template
Changes typically originate in the user area, though the software design team may initiate changes. A change request should be submitted using a Design Change Request Template. At a minimum, ITSW108-1 DESIGN CHANGE REQUEST FORM should capture the project name, project number, project manager’s name, the name of the requestor, request date, resolution requested by date, description of and reason for change, impact on scope and/or deliverables, impact on time and cost, impact on resources and quality, change accepted or rejected, and sign-off signatures from those in charge.
The Project Manager, Systems Analyst, and Software Designer should review each proposed design change and determine what action to take. Questions to consider include:
- Do the benefits of the change outweigh its costs?
- Can the change be implemented in an acceptable amount of time?
- Is the change functionally necessary?
- Can the change be implemented in a subsequent release of the product?
The Software Designer should estimate potential delays caused by the change, add this information to the Design Change Request Form, and forward it to the project’s Systems Analyst. The Project Manager should rework the project schedule and submit the form to User Management for its approval.
Design Change Request Template Details
Format: Microsoft Word 2013 (.docx)
Manual: IT Poicies and Procedures Templates
Category: Software Development
Procedure: Software Design Change Procedure ITSW108
There are no reviews yet.