Project management is, by its very nature, a complex process which often includes many people, influences, variables, tasks, and other considerations to successfully manage. In order to be successful a project manager must effectively use various tools and methodologies to communicate and manage the project. Two of the most important characteristics of a successful project are documentation and accountability. Project documentation is used to formally capture and communicate important project information so it is available to everyone who needs it. The documentation must be carefully managed and updated as any changes occur in order to prevent gaps and/or overlaps in project work. Accountability must be established so the project team and stakeholders understand who is responsible for the work to be performed. If tasks are not specifically assigned and managed, they will sit idle and may significantly impact the overall project performance. The issue log is one example of project documentation and accountability. The issue log is used throughout a project’s lifecycle to capture any issues brought forward, communicate the issues to the project team and stakeholders, establish categories and priorities of all issues, assign responsibility to each issue, and ensure that each issue is resolved with minimal impact to the project’s performance. Like most other project documentation, the issue log should be reviewed by the project team regularly to ensure issues are being resolved. The document should be updated and communicated to all project stakeholders as updates are made. Sample Issue Log with Explanations: Issue Log Project: Date: Description Priority Category Reported By Assigned To Status Date Resolution/ (H, M, L) Resolved Comments This should be a Detailed High, Assign to a Who reported Who is the What is the What date What was the standard description of the Medium or category. the issue? assigned status of the was the resolution or numbering issue. Low priority. to? issue? issue what is being system. resolved? done to resolve the issue?
Project management is, by its very nature, a complex process which often includes many people, influences, variables, tasks, and other considerations to successfully manage. In order to be successful a project manager must effectively use various tools and methodologies to communicate and manage the project. Two of the most important characteristics of a successful project are documentation and accountability. Project documentation is used to formally capture and communicate important project information so it is available to everyone who needs it. The documentation must be carefully managed and updated as any changes occur in order to prevent gaps and/or overlaps in project work. Accountability must be established so the project team and stakeholders understand who is responsible for the work to be performed. If tasks are not specifically assigned and managed, they will sit idle and may significantly impact the overall project performance. The issue log is one example of project documentation and accountability. The issue log is used throughout a project’s lifecycle to capture any issues brought forward, communicate the issues to the project team and stakeholders, establish categories and priorities of all issues, assign responsibility to each issue, and ensure that each issue is resolved with minimal impact to the project’s performance. Like most other project documentation, the issue log should be reviewed by the project team regularly to ensure issues are being resolved. The document should be updated and communicated to all project stakeholders as updates are made. Sample Issue Log with Explanations: Issue Log Project: Date: Description Priority (H, M, L) Category Reported By Assigned To Status Date Resolved Resolution/ Comments This should be a standard numbering system. Detailed description of the issue. High, Medium or Low priority. Assign to a category. Who reported the issue? Who is the assigned to? What is the status of the issue? What date was the issue resolved? What was the resolution or what is being done to resolve the issue?
Issue-Log.docx