Issue Log

What is an issue log?

Trouble is literally everywhere in our daily life. In fact, the concept of a problem in project management is not much different than in real life. Accordingly, a problem is a situation or condition that occurs up-to-date. It is called a project issue when these conditions or conditions have any effect on the project goals.

Issue log is the project artifact that is used for monitoring and recording the necessary information about ongoing issues. The events and factors under discussion or in dispute between project stakeholders are handled by using an issue log. An issue log ensures that the ongoing issues in the project are tracked by the project team and are under control.

Documentation and accountability are two important things to take care of in order to complete a project successfully and to achieve expected value delivery. The issue log is a live document that should be kept updated during a project’s lifecycle. Any new issues are identified, issues are communicated with the project team and stakeholders of a project by using an issue log

 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.

In a project issue log generally, the following information is given but they are not limited to them;

  • The name of the issue,
  • Description of the issue,
  • Category,
  • Priority,
  • Reporting source,
  • Responsible person to deal with the issue,
  • Current status of the issue,
  • Endnotes,

Issue log is a project artifact categorized as log and register artifacts, it is generally used in project work performance domain.

In project management it can be a useful input in many areas of project work performance domain, it can be used while identifying stakeholders. Right stakeholders can be extracted from the issue log. Also, it is useful while identifying risks of the project as well as performing a qualitative risk analysis, managing and controlling quality. It should be communicated efficiently in order to make all stakeholders and the project team informed about the ongoing issues.

An issue log is also very useful to be used in monitoring and controlling processes for measurement purposes. Especially while thinking about possible solutions and corrective actions, you have to know the ongoing issues very well to plan a good response to align the project on its track again.

See also;

Assumption Log

Change Log

Risk Adjusted Backlog