Issue Management starts when you are planning the project and lasts throughout the entire project lifecycle.
Even before a project starts there can be issues already in play. You’ll need to identify issues in the planning stage and document them in an issues log. Issues Logs can be as simple as a text document with a table in it or a simple spreadsheet or can utilize specific software systems designed for logging issues. Issues log should be regularly monitored and updated throughout a project as part of your general project reporting and as issues come up.
The content of your issues log may vary, but generally there are some basic fields that most issues logs will contain. These include: Issue Reference, Name, Description, Severity, Impact. Then issue updates may include fields such as a date, description, status and actions. It really is imperative to keep a good issues log. Just the act of having to update a log keeps you on top of where things are at and pushing along the actions required. The other good aspect of having well documented issues is that when things hit the fan, and they sometimes do, then you have a detailed, documented trail of the actions you have been taking to rectify or resolve issues.
There are some issues that require documentation beyond the basic Issues Log. This is where an issue requires further analysis and consideration of impact of possible actions – often where escalation is required. Where this is the case I use an ‘Issue Report’ or ‘Issue Description’ which is a concise report that descibes the issue background, impact (time, cost, quality) and potential actions with their time, cost and quality impacts.
Keeping on top of issues that arise is imperative for project managment success. It can stop little issues from becoming ‘showstoppers’, it keeps your project moving on the right path and it fosters confidence in you as a manager – from your stakeholders and your team.
Related posts:
