Friday, May 29, 2009

Step 06: Issues Management

Description

Objective

 

To       

 

            -  resolve issues affecting the success of the project,

 

in a way that

 

            -  identifies issues affecting the project,

 

            -  assesses the extent to which issues affect the project,

 

            -  identifies actions to resolve issues,

 

            -  involves the appropriate level of management to make decisions on issues,

 

            -  tracks progress on issues,

 

so that

 

            -  the project can be carried out as planned.

 

Overview

 

There will always be issues that arise during the course of a project.  Some of these issues may have a bearing on the project, and some will be of little consequence.

 

Issues can arise from within the Project Organization and from the environment that impacts the project.

 

Any issues that arise should be evaluated and dealt with as efficiently and effectively as possible.

 

An issue can often linger on, even after it has supposedly been resolved, so it is important to track issues to complete resolution. 

Task .010          Identify Project Issue

Identify and describe an issue that is thought to affect the project.  Determine whether to pursue the issue and, if any further research is required before assessing the issue, assign someone to research the issue.

 

Update Issue Log as follows:

 

            -  Assign a unique Issue No.

 

            -  Issue Title

 

            -  Type

 

            -           Internal, where the issue can be resolved by the project team.

 

            -           External, which cannot be resolved by the project team, but requires client or Project Board resolution.

 

            -  Priority

 

            -           0  irrelevant, since it does not impact the project in any way,

 

            -           1  low, whereby the unresolved issue will not impact current stage schedule,

 

            -           2  medium, whereby the issue will impact the stage schedule if not resolved within four weeks,

 

            -           3  stage stopper, whereby the issue must be resolved for work to continue on the current stage,

 

            -           4  project stopper, whereby the issue must be resolved by the end of the stage for work to continue on the project.

 

            -  Originator's Name

 

            -  Assigned To

 

            -  Response Date

 

            -  Status (Open or Closed)

 

Forward the issue to the appropriate team member, client, coordinator or Project Board member for assessment and recommended resolution.

Task .020          Assess Impact of Issue

Consider the potential impact of the issue on the project:

 

            -  what happens if the issue is not actioned?

 

            -  will it impact project scope?

 

            -  will it impact the quality of the final product?

 

            -  will it cause the project to go out of tolerance?

 

            -  will it impact resource usage?

 

            -  will it change the project benefits?

 

            -  will it increase project risk?

 

Determine how the issue might be resolved.

 

Update the Issue Log with the recommended "Resolution".

Task .030          Resolve Issue

Determine whether the to accept the recommended resolution.

 

If the recommendation is accepted, and no additional effort is required, execute the resolution.  Set Issue status to "Closed".  Update Close Date.

 

If additional effort is required to execute the recommended resolution, create a Change Request.  Set Issue status to "Closed".

 

If the recommendation is unacceptable, then determine next steps.  Issue status remains "Open".

No comments:

 
hit counter
unique hit counter