Complete the Project Name, NC, Project Manager Name, and Project Description fields.
1-ID: A unique ID number used to identify the issue in the issue tracking log.
2-Current Status: This column should be populated with the issue's current status.
- Open: The issue is currently open but has not yet been addressed.
- Work In Progress: The issue is being actively worked to develop a resolution.
- Closed: The issue is no longer considered an active project threat and can be closed with or without resolution.
Some other potential options include:
- Late: The issue resolution is not yet resolved and it is past the expected resolution date.
- On Hold: The issue has been put on hold.
- Combined: Two issues found to be similar have been combined.
3-Priority: This column should be populated with the priority of the issue. Valid options include the following: High, Medium, Low. These are defined as follows:
- Critical: Issue will stop project progress if not resolved.
- High: Issue will likely move the project back in terms of budget or timeline, or will materially affect quality or scope.
- Medium: Issue will have material effect on project, has potential to be moved to high category and/or requires significant resources to manage.
- Low: Issue is expected to have a moderate effect on the project, but will require resources to address.
4-Issue Description: This column should be populated with a description of the issue.
5-Assigned to Owner: This column should be populated by the name of the issues owner. The individual most responsible for working towards resolving the issue.
6-Expected Resolution Date: This column should be populated with the date that the issue is expected to be resolved.
7-Escalation Required (Y/N): This column should be populated with “Yes” if the program/project manager feels an issue needs to be escalated and “No” if escalation is not needed to resolve the issue.
8-Impact Summary: This column should be populated with a description of the impact of the issue. The impact may be expressed in terms of one or more of the following: schedule, scope, resources, and space. The impact description should also include a reference to any milestones impacted.
9-Action Steps: This column should be populated with the proposed steps to address the issue. Examples include, but are not limited to, developing alternatives analysis or submitting a change request.
10-Issue Type: This column should be populated with the issue type. Valid options include the following: FRI, Procedural, System, Other. These are defined as follows: o Informational: The issue was generated and logged in response to a request for information external to the immediate project/project team.
- Procedural: The issue impacts process or procedure.
- System: The issue impacts systems (hardware or software).
- Other: The issue impacts other areas.
11-Date Identified: This column should be populated with the date that the issue was identified.
12-Associated ID(s): This column should contain the project ID of any associated milestones that may be impacted by an issue or that the issue is dependant upon for resolution. Please note, this value may require coordination with other programs/project managers or the PMA.
13-Entered By: This column should be populated by the name of the individual who first identified the issue.
14-Actual Resolution Date: This column should be populated with the date that the issue was actually resolved.
15-Final Resolution & Rationale: This column should be populated with a description of the final resolution & rationale of the issue. The resolution may be expressed in terms of one or more of the following: schedule, scope, resources, and space. The resolution description should also include a reference to the milestones impacted.
0 Comment: