Вы находитесь на странице: 1из 7

Issue Management Plan

Project Name: Project Management Improvement

EXAMPLE

Disclaimer: This example is based on the Project Management Improvement project, but is not necessarily an actual case for that project.

Prepared By: Person-A

Title: Project Manager Version No: 1

3.3.5 Example Issue Management Plan, v2.2

Page 2

Document Change Control


The following is the document control for revisions to this document.
Version Number
1

Date of Issue
3/5/2007

Author(s)
Person -A

Brief Description of Change


Initial Plan

Definition
The following are definitions of terms, abbreviations and acronyms used in this document. Term Definition

3.3.5 Example Issue Management Plan, v2.2

Page i

Table Of Contents
1. ISSUE MANAGEMENT GOALS AND APPROACH.........................................1 2. ISSUE MANAGEMENT CATEGORIES AND RULES.......................................1 LOW AND MEDIUM IMPACT ISSUES WILL BE MONITORED AND REPORTED IN MONTHLY STATUS REPORTS. HIGH IMPACT ISSUES WILL BE MONITORED WEEKLY AND REPORTED AT BIWEEKLY TEAM MEETINGS AND BIWEEKLY SPONSOR MEETINGS.........................................1 3. ROLES AND RESPONSIBILITIES....................................................................2 4. THE ISSUE MANAGEMENT PROCESS...........................................................2 5. TOOLS................................................................................................................3

3.3.5 Example Issue Management Plan, v2.2

Page ii

1. Issue management goals and approach


A goal of this project is to identify issues as soon as they arise and to resolve them expeditiously. All team members are enjoined to be vigilant, particularly in their areas of expertise, but also to raise issues outside of their areas of specific responsibility when they become aware of them. The issue management goals and approach for this project include: Informal monitoring for the identification of issues via team meetings Informal documentation of low and medium impact issues via periodic status reports to project stakeholders Formal documentation of high impact issues using the attached issue management log

2. Issue management categories and rules


The project will use the following categories and rules to manage issues: Priority Categories Low impact (no project delay but needs resolution) document in monthly status report, assign to project manager for resolution Medium impact (some project delay, but progress can continue) document in monthly status report, assign to project manager for resolution High impact (significant project delay or show-stopper) document and track in issue log, report immediately to project sponsors, consult on appropriate assignment for resolution responsibility and target date for resolution

Escalation Rules Monitoring Frequency

Any high impact issue with missed resolution target date will be escalated to project sponsor for further action. Low and medium impact issues will be monitored and reported in monthly status reports. High impact issues will be monitored weekly and reported at biweekly team meetings and biweekly sponsor meetings.

3. Roles and responsibilities


The project manager is assigned the role of issue manager. The issue manager is responsible to assess and record any identified issue assign a priority to the issue assign a resolution due date for the issue and the person responsible to resolve it monitor the status of issue resolution escalate issues as required by the escalation rules communicate issues to the project team and others report issue management activity according to communications plan manage the issue tracking log The project sponsors are assigned the role of issue escalation decision makers. The issue escalation decision makers are responsible to resolve or to provide guidance to resolve issues escalated to them

4. The issue management process


For each issue identified during project execution: 4.1 Identification: Any identified issue will be communicated to the issue manager at the earliest opportunity. 4.2 Prioritization: The issue manager will apply prioritization rules to the issue. 4.3 Tracking: The issue manager will record and track low and medium impact issues in the monthly status report and high impact issues in the issue log. 4.3 Escalation when required: If escalation rules are satisfied, the issue manager will escalate the issue immediately. 4.4 Assignment of issue for resolution: The project manager is responsible for resolution of all low and medium impact issues. For high impact issues, the issue manager will consult with relevant experts and stakeholders, assign a due date for resolution and a specific person responsible for resolving the issue. 4.5 Monitor resolution status and evaluate for escalation: The issue manager will track the status of issues and escalate issues when escalation rules are satisfied. 4.6 Communication: Issue statuses of high impact issues will be reviewed in biweekly sponsor meetings and biweekly team meetings. Escalation decision makers will be notified at the earliest opportunity when an escalation occurs. An issue summary, including any issues resolved in the period since the last report, will be published to stakeholders and customers with the monthly project status report. 4.7 Close resolved issues: The issue manager will record the action taken to resolve the issue when closing a resolved issue.

5. Tools
Issue log
See attached issue log template.