Recording an Informal Issue

C.

An informal issue is a problem or concern that is not yet formally raised within the project or program management structure. It is typically identified through informal channels, such as conversations, emails, or meetings.

When an informal issue is identified, it should first be recorded in the Daily Log. The Daily Log is a record of all issues, risks, and other relevant information that arises during the course of the project or program. It is a tool for capturing information quickly and easily, without the need for formal documentation or analysis.

The Daily Log is maintained by the project manager or program manager, and it is typically used as a reference tool for tracking progress and identifying trends over time. It provides a central repository for all project or program-related information, which can be used to inform decision-making and to support effective communication.

Once an informal issue is recorded in the Daily Log, it can be reviewed and analyzed to determine if it needs to be formally raised as an issue or risk. If it does, it can be added to the Issue Register or Risk Register, which are more formal tools for managing and tracking issues and risks.

The Issue Register is a document that captures all issues that have been formally raised, and it includes information such as the issue description, priority, status, and resolution. The Risk Register is a similar document that captures all identified risks, and it includes information such as the risk description, probability, impact, and mitigation plan.

In summary, when an informal issue is identified, it should first be recorded in the Daily Log. This allows the project or program manager to track the issue and determine if it needs to be formally raised as an issue or risk, and added to the Issue Register or Risk Register for formal management and tracking.