You are on page 1of 1

Eng.Mohamed Ezzat Abouzied 0592803214 ezat104@gmail.

com

- Throughout the life cycle of a project, the project manager will normally face problems, gaps,
inconsistencies, or conflicts that occur unexpectedly and that require some action so they do
not impact the project performance. The issue log is a project document where all the issues
are recorded and tracked. Data on issues may include (Issue type, who raised the issue and
when, Description, Priority, who is assigned to the issue, Target resolution date, Status, Final
solution.
1. will help the project manager effectively track and manage issues , ensuring that they are
investigated and resolved. The issue log is created for the first time as an output of thi s
process (manage and direct project work), although issues may happen at any time during the
project. The issue log is updated as a result of the monitoring and control activities throughout
the project’s life cycle.
2. The issue log is used to document and monitor who is responsible for resolving specific issues
by a target date.
3. New issues raised as a result of this process (manage and direct project work) are recorded in
the issue log.
4. The issue log is used to check that there is no open issue.
5. Many times, a deliverable that does not meet the quality requirements is documented as an
issue log.
6. The issue log is used to identify issues such as lack of resources, delays in raw material
supplies, or low grades of raw material.

7. Information about issues is communicated to impacted stakeholders.


8. The issue log is updated to reflect any communication issues on the project, or how any
communications have been used to impact active issues.

9. The issue log provides the project’s history, a record of stakeholder engageme nt issues, and
how they were resolved.

10. Issues recorded in the issue log may give rise to individual project risks and may also influence
the level of overall project risk.
11. The issue log should be updated to capture any new issues uncovered or changes in currently
logged issues.
12. Where issues are identified as part of the Implement Risk Responses process, they are
recorded in the issue log.
13. The issue log is used to see if any of the open issues have been updated and necessitate an
update to the risk register.
14. Where issues are identified as part of the Monitor Risks process, these are recorded in the
issue log.
15. The issue log records issues that may introduce new stakeholders to the project or change the
type of participation of existing stakeholders.

Eng.Mohamed Ezzat Abouzied 0592803214 ezat104@gmail.com

032
017

You might also like