A project manager who is managing a critical project in a multinational company is conducting a progress meeting with all team members. During the meeting, one of the team members states that they are facing a critical problem that will prevent them from completing their assigned task.
What should the project manager do?
When a team member reports a critical problem that hinders task completion, it indicates an active issue, not just a potential risk. The immediate concern is to address the issue directly. Scheduling a meeting with the concerned team member to review and update the issue log together ensures the problem is documented and addressed appropriately. This approach allows the project manager to understand the specifics, prioritize the issue, and develop a resolution plan collaboratively. It provides a structured way to manage and mitigate the problem efficiently.
it is not an issue as yet, it's still a risk, hence C
I think that since it is decided that the critical task cannot be completed on time, it is an issue and not a risk
But is a problem "critical problem"
The key word is "critical problem". It is no more risk but an issue. So I will go with B.
Option C, reviewing the risk register with the team member to find the proper response action for this issue, is not the most appropriate action in this situation. This is because the issue is already happening, and the team member is currently facing it. The risk register is used to track potential risks to the project, and it is used to develop mitigation plans for those risks. However, in this situation, the risk has already happened, and the team member is currently facing it. Therefore, the risk register is not the best tool to use to address this issue.
C looks more related as it provides an resolution rather than an update to issue log.
Issue is tangible, so B is the answer.
I will go with B
First of all, PM need to meet with member to get understanding member concern in detail
Answer should be B because Issue log contains the list of closed and ongoing issues. Issue is just discovered by the developer so not listed in the issue log yet.
I mean C
LOOK AT IT THIS WAY. EVER HEARD OF SECONDARY RISKS? FROM PMBOK? CHECK THE REGISTER AND CHECK FOR APPROPRIATE ACTIONS. THIS IS MUCH MORE PROACTIVE RATHER THAN REVIEWING A DOCUMENT WITH A TEAMMATE. LOOK FOR ACTIONS PEOPLE!
B. Schedule a meeting with the concerned team member to review and update the issue log together
If the solution to the critical problem(risk response) is already present in the risk register, then reviewing the risk register with the team member (Option C) can be an efficient approach to quickly address the issue. This would allow the project manager and the team member to identify the response actions and apply them promptly.
why not C ?