Project Management

Please login or join to subscribe to this thread

Issues...RAID Log

linkedin twitter facebook   PMO   Risk Management   Schedule Management   Scheduling  
avatar
Roy Rogers Az, United States
Is PM the sole responsible person to update or capture Risk Action Issue Decisions log?. OR stake holders can do this and.... PM is responsible for tracking and assessing the impact of those RAID items for project cost, time & scope and take corrective actions?.
Sort By:
< 1 2 >
avatar
Kevin Drake Perth, Western Australia, Australia
The input into the RAID log will come from many sources such as project documentation (charter, business case, intake form, meeting minutes, et cetera), sponsor, project team members, and other stakeholders. Another valuable source would be documentation (risks, issues, lessons learned, et cetera) from other projects that may be similar in nature.
avatar
Sante Delle-Vergini, PhD Senior Project Manager| Infosys Melbourne, Victoria, Australia
The project team is generally responsible for capturing risks, but the PM is accountable.
avatar
Lenka Pincot Chief of Staff to the CEO| Project Management Institute Paris, France
Agree with Sante. In practice there are meetings where the team discusses or brainstorms the risks, issues etc. and PM captures that in the log. It is responsibility of PM to keep the log, getting inputs from the others and also get inputs to update the log.
avatar
Kevin Smith Project Management Consultant| Prime Focus Project Management West Bloomfield, Mi, United States
The project manager has the sole responsibility for capturing Risks, Action, Issues, and Decisions within the RAID log. While project team resource are those who would ideally identify these items, it is the project manager's responsibility to track, ensure mitigation, assess, etc. Typically project resources are not familiar with how to accurately capture a risks, actions, etc while clearly identify the area in which they fall. I am interested in hearing other perspectives.
avatar
Karan Shah Bangalore, Karnataka, India
To qualify all the above excellent responses, the RAID log should have just one "updater". If it is open for all-and-sundry to update, the project would end up in a multitude of uncoordinated versions.

Communication strategies have to be defined and enforced that allow all project stakeholders to inform the "updater" of modifications or additions to the log.

The "updater" then, periodically, disseminates this information to the rest of the project organisation.

This "updater" is usually the PM or a project coordinator.
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
It really depends on who is directly consuming the information within that RAID log. If it is going to be directly accessed by external stakeholders, then I'd agree that the PM should be the one holding the pen but taking input from the team and other stakeholders to do so.

However, if it is a strictly team-level repository and the PM extracts and curates content from it to share with external stakeholders, then I'm a fan of having those who have the best awareness of the data do the updates themselves.

Kiron
avatar
Penny Hansberry-Clark Project Manager - PMP| SSM Health Loganville, Wi, United States
I agree. The PM should be the only contributor to the RAID log. The team is fully engaged in identifying, mitigating, resolving issues/risks. However, the PM is accountable to leadership. The PM must have a complete understanding of all data on the RAID Log as well as be able to explain clearly to leadership.
avatar
Thomas Walenta Global Project Economy Expert Hackenheim, Germany
Have seen RAID logs on small projects/teams only, and then it is OK if someone owns the log and maintains it, could be the PM or a PMO.
In larger projects, I have seen and used separate logs for risks, decisions, actions and issues, as they result from different types of meetings/events and are governed by different processes. Risks should be identified by anyone, but assessed and elaborated by SMEs. Decisions are made on different levels, steering committee, customer meeting, less on team meetings. Actions typically are shortlived and are agreed and checked in (team) meetings.
avatar
Peter Rapin Subject Matter Expect; Project Delivery| Independent Consultant Ontario, Canada
Just because a person is accountable does not mean they must do the action themselves. The PM is accountable to deliver the project which includes the management of all project elements, cost, timeliness, quality, scope, risk, etc. However someone in the team may be assigned to each of these elements of project management accountable to the PM. In this management structure the Risk Manager would be responsible for the RAID log with input from the team. Note that the PM may chose to retain Risk Management within his/her portfolio.
avatar
Latha Thamma reddi Sr Product and Portfolio Management (Automation Innovation)| DXC Technology Mckinney, Tx, United States
The project team is generally responsible for capturing risks, but the PM is accountable.
...
1 reply by Peter Rapin
May 19, 2023 4:13 PM
Peter Rapin
...
As defined in the Project Charter and Project Plan
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"There is not one wise man in 20 that will praise himself."

- William Shakespeare

ADVERTISEMENT

Sponsors