실행 단계에 있는 프로젝트에 새로운 프로젝트 관리자가 배정되었습니다. 몇몇 주요 이해관계자가 새 프로젝트 관리자에게 프로젝트에 심각한 문제가 있다고 알립니다.
새로 배정된 프로젝트 관리자는 문제를 이해하기 위해 먼저 무엇을 해야 할까요?
정답: B
According to the PMBOK Guide, 7th edition, an issue is a point or matter in question or in dispute, or a point or matter that is not settled and is under discussion or over which there are opposing views or disagreements1. Issues can arise from various sources, such as changes, risks, defects, conflicts, or assumptions1. Issues can affect the project performance, scope, quality, schedule, cost, or stakeholder satisfaction1.
An issues log is a project document used to capture and track issues until they are resolved1. The issues log typically contains information such as the issue description, priority, owner, status, resolution, and impact1. The issues log is updated throughout the project life cycle as new issues are identified, analyzed, and resolved1.
In this scenario, the newly assigned project manager is informed by a few key stakeholders that the project has some serious issues. The first thing that the project manager should do to understand the issues is to review the issues log to ensure the issues are captured. This will help the project manager to get an overview of the current state of the project, and to identify the nature, scope, and impact of the issues. It will also help the project manager to verify if the issues have been properly documented, prioritized, and assigned to the responsible parties. Reviewing the issues log will also enable the project manager to plan the next steps to address the issues, such as communicating with the stakeholders, performing root cause analysis, implementing corrective actions, or escalating the issues if needed1.
The other options are not as effective as option B. Option A, escalating the issues to the project sponsor, may be necessary if the issues are beyond the project manager's authority or control, but it is not the first thing to do. The project manager should first review the issues log to understand the issues and their implications, and then decide if escalation is required or not. Option C, checking the risk management plan to ensure there is a strategy to address the issues, may be helpful, but it is not sufficient. The risk management plan provides guidance on how to manage risks, not issues2. Risks are uncertain events or conditions that may have a positive or negative effect on the project objectives, while issues are certain events or conditions that have already occurred and have a negative effect on the project performance1. Therefore, the risk management plan may not cover all the issues that the project faces, and the project manager should review the issues log instead. Option D, asking the key stakeholders to discuss the issues with the project team, may be beneficial, but it is not the first thing to do. The project manager should first review the issues log to get a clear picture of the issues, and then facilitate the discussion between the stakeholders and the team to resolve the issues.
1: PMBOK Guide, 7th edition, page 101 2: PMBOK Guide, 7th edition, page 113
