’s Top 3 Software RecommendationsLet work for you.Start Free TrialWork smarter with Wrike.Try for FreeIncrease productivity with Smartsheet.Try Smartsheet for FreeWhy are logs important?
Logs are one of the most important tools for project managers. A log is simply a list of items that includes key information about each item. These are some of the benefits of using a log:
To remind the project team
To provide a visible method of verification
To give everyone in the team an equal opportunity to raise a concern
To help you focus a meeting or discussion
To assist the project manager to monitor progress
To be proactive
To document resolutions
The RAID log is an important project management log that can be used to manage risks and issues. There will always be issues during the execution of a project. Risks are problems that have yet to occur. The RAID log allows you to keep track of both the risks and the issues that may arise.
What is a RAID log and how do you use it?
A RAID log is a tool for project management. It allows the project manager to log, document, or track the risks, assumptions and issues of a project. One version of the RAID log substitutes assumptions for actions and decisions for dependencies. Another version combines them to create a RAAIDD Log. The version a team uses will depend upon what they consider most helpful in managing their project.
Why would you need a RAID log?
The project execution phase begins after the project planning phase. The project monitoring and control phase is also underway. This allows you to monitor progress and measure performance if everything is going according to plan. A RAID log can be used to track risks, issues, and any other circumstances that could affect or influence the project. It is possible to see the importance of each item in a RAID log by looking at it.
A risk is a project’s exposure to an unpredicted future event that could have an impact on its completion. The RAID log allows the project manager to identify potential risks and the situations, activities, or events that could increase or decrease the likelihood of the risk becoming a problem. The project manager can assess the likelihood of it happening and plan for the resources or actions to minimize it.
An assumption is a belief that a piece or information is true. There is no evidence to support it. Project managers may assume that something will remain the same or change as the project team executes their tasks. It is important to check and track whether assumptions are still valid. If assumptions are found to be false, it is important to make changes in the plan and execution.
The other A is for action. This is required to complete a task, or respond to a problem. The owner of the action must be able to complete it by a specific date or time. The project manager can keep track of the date and any follow-ups.
An issue is a problem that has occurred and must be identified. It can affect the project in many ways. For example, it may delay or prolong the completion of the project, add complexity, or require additional resources. The project manager must keep track of all issues, their severity, and impact and communicate how they are being handled and resolved.
A dependency is a project item that is required in order to allow the plan to move forward without any problems. It could be a deliverable or a resource. It doesn’t matter what it is, it must still be presented or delivered for the project to move forward. The project manager should keep track of all dependencies and help to speed up delivery if possible.