Sunday, July 17, 2016, AM | Leave Comment
Issues are more than just common problems. They are problems that meet specific criteria. An issue is a formally-defined problem that will impede the progress of the project and cannot be totally resolved by the project team without outside help.
The processes used to manage issues can be simple or more rigorous depending on the size of the project.
Use the following process to manage issues on large projects.
Formally define the issue on an Issues Form
The first step is to document the nature of the issue. If a problem cannot be documented, it cannot be solved.
Solicit potential issues from any project stakeholders, including the project team, clients, sponsors, etc.
The issue can be surfaced through verbal or written means, but it must be formally documented using an Issues Form.
Determine if the problem is really an issue
The project manager determines whether the problem is impeding the progress of the project and whether the problem needs help outside the team to resolve. If so, it can be classified as a true issue.
Enter the issue into the Issues Log
If it is an issue, the project manager enters the issue into the Issues Log.
Determine who needs to be involved in resolving the issue
By definition, an issue needs help outside the project team to resolve.
The project manager now determines who needs to be involved in resolving the issue. The sponsor may or may not be involved.
For instance, the problem may be contractual and require resolution from the Purchasing Department.
However, at some point the alternatives will be discussed and a resolution will be made.
It is important to understand up-front who needs to be involved in making this final issue resolution.
Assign to team member for analysis and alternatives
The project manager assigns the issue to a project team member for investigation (the project manager could assign it to himself).
The team member will investigate options that are available to resolve the issue. For each option, the team member should also estimate the impact to the project.
Gain agreement on resolution
The various alternatives and impact on schedule and budget are documented on the Issues Form.
The project manager should take the issue, alternatives and project impact to the appropriate stakeholders (from step 6 above) for discussion and resolution.
The project manager may want to make a recommendation from among the alternatives as well.
Close the Issues Log
The project manager documents the resolution or course of action on the Issues Log.
Close the Issues Form
The project manager documents the issue resolution on the Issues Form and then closes and files this document.
Add action plan to the schedule
Once a resolution is agreed upon, the appropriate corrective activities are added to the schedule to ensure the issue is resolved.
Communicate through the Status Report
The project manager communicates issue status and resolutions to project team members and other appropriate stakeholders through the methods established in the Communication Management Plan, including the project Status Report.
Smaller projects do not need all of these steps. For instance, the issue can be documented directly in the Issues Log without the need for the separate Issues Form.
This column is © copyright to www.Method123.com and originally appeared in their weekly project management tip newsletter.
Use the best project management process in the world. Method123 Project Management Methodology (MPMM) is used by tens of thousands of customers around the world.
Take a test drive with the free trial download.
Buy MPMM today – NOW with extra program management and IT development modules.
Get your project started quickly with a pre-built set of great project management templates.