        |
|
 |
|
|||||||||||||||||
|
|||||||||||||||||
 |
CHANGE CONTROL PLAN Work Product Change Control Summary
Change Control Procedures Single Author - A document with this procedure will be updated when necessary. The administrator of this document may update the document at any time needed. Changes made will be written at the bottom in a change summary. If others need to make changes to this document, they must contact the administrator, who will then make the changes. If this document is stored on the web page, then see the procedure labeled "Dreamweaver" Multi Author - The tool of choice for this procedure will be CVS. This mainly applies to source code, which will be updated by all team members. CVS takes care of documenting the changes made to a document. Dreamweaver - This procedure applies to the team web site. When necessary changes are made to documents and they are to be posted on the site, team members must follow the web procedure, which is linked from the team web site. If a new page is to be created, team members must contact the web administrator. Formal Change - Whenever someone determines that some aspect of an accepted work product should be changed, then he/she is to submit a change proposal request to the Change Control Board via Formal Change Request Form, which is linked below. Once a change proposal has been submitted to the Change Control Board, the change proposal is given to the administrator of the work product or the person who may be impacted by the change. These parties are responsible for producing an estimate of the effects of implementing the proposed change. The Change Control Board will then assess the following:
Once the impact of the proposed change to each area is assessed, the Change Control Board must make a decision whether to accept or reject the proposed change. The Change Control Board may reject a proposed change out-of-hand if it determines that the cost of formally assessing the impact of the change outweighs its perceived benefit. Since defects are treated like all other change requests, the Change Control Board selects for correction only those defects which represent an acceptable benefit/risk trade-off based on the phase of the project and the distance from the next important milestone. If accepted, the assessed impact on the development schedule must be incorporated into the existing schedule and a new schedule produced. If the Change Control Board deems it necessary, trade-offs between time, function, and manpower may be made in an attempt to mitigate the effects of change to the existing schedule. However, in no circumstances will changes be approved without sufficient consideration of their associated schedule implications. Regardless of whether a change is approved or rejected, the following information is recorded by the defect tracking system and made available to the party submitting the change proposal (and any other interested parties that desire to monitor the progress of the work product):
The Change Control Board for this project will consist of all team members. For any given request, the Board leader will be the administrator of the work product in question. All decisions will be documented on the web site. Formal
Change Request Form An automated HTML form will be posted on the site, which allows developers to suggest changes at any time. The form will contain the area of the change or issue, who is responsible for it, etc. All completed requests will also be posted on the web once completed. Click Here Submitted Change Requests All submitted requests will be logged on the web page. Once a week, the change request list will be updated on the web page. When a decision has been made, the admin for the document will be notified, and he is responsible for making the changes.
Version History: |
