APPENDIX A.9: PROJECT ISSUE

Project issue
Project name   Status Open/closed
Issue ID   Issue type RC = Request for change

OS = Off-specification
C = Concern or question

Date raised   Raised by  
Author   Attachment If any needed to assist in understanding the issue.
Issue description A description of the issue.
Accept/reject Reason

(reject only)

The issue will be assessed, and a decision will be made as to whether it is unreasonable with no grounding, and therefore is ‘rejected’, or it is reasonable and well-grounded, so is therefore ‘accepted’. If a decision is made, the ‘decision’ field of the issue form should be updated accordingly, or if no decision is made it should be left blank.

If the decision is to ‘reject’ the issue, the decision field of the issue is updated to ‘rejected’, with an explanation of the reason it was rejected. The status of the issue is updated to ‘closed’ and the action log is updated to reflect the same. A copy of the updated project issue form is sent to the project manager and the issue originator.

Priority High/medium/low/cosmetic
Impact analysis What would be the impact on other products and the project plan if the decision is made to implement any change?
Proposed change What product/s would have to change? Have any of them already been signed off?
Decision  
Decision date   Signed off by
Closure date    
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.133.146.237