According to the PMBOK Guide, 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 An issue log is a project document that provides a mechanism for tracking and monitoring issues until they are resolved1 The issue log typically contains information such as the issue description, the issue type, the issue owner, the issue priority, the issue status, and the issue resolution1 The issue log is updated throughout the project as new issues arise and existing issues are resolved1
In the given scenario, the project manager is executing a project where an external vendor will provide some deliverables. After awarding the contract to the vendor, the project manager is informed that the vendor is running behind schedule on a separate project. Finding another vendor will exceed the budget. This situation presents an issue that affects the project schedule, cost, and quality, and requires immediate attention and resolution. The project manager should update the issue log first to document the issue, assign an owner, and monitor the status of the issue2 Updating the issue log will also help to communicate the issue to the relevant stakeholders and facilitate the issue management process2
The other options are not the best choices for the following reasons:
Option B: Lessons learned register. A lessons learned register is a project document that captures the knowledge gained from the project and provides a basis for future actions and decisions. The lessons learned register is updated throughout the project as lessons are learned and validated. However, updating the lessons learned register is not the first action that the project manager should take in response to the issue. The project manager should first document and address the issue in the issue log, and then update the lessons learned register with the relevant information and insights after the issue is resolved.
Option C: Stakeholder engagement plan. A stakeholder engagement plan is a subsidiary plan of the project management plan that identifies the strategies and actions to effectively engage project stakeholders throughout the project life cycle. The stakeholder engagement plan is updated as needed to reflect the current and desired levels of stakeholder engagement. However, updating the stakeholder engagement plan is not the first action that the project manager should take in response to the issue. The project manager should first document and address the issue in the issue log, and then update the stakeholder engagement plan if the issue affects the stakeholder expectations, interests, or influence.
Option D: Risk register. A risk register is a project document that records the details of identified individual project risks and other information related to risk analysis and risk response planning. The risk register is updated throughout the project as new risks are identified and existing risks are analyzed, prioritized, and responded to. However, updating the risk register is not the first action that the project manager should take in response to the issue. The project manager should first document and address the issue in the issue log, and then update the risk register if the issue triggers a risk response or creates a new risk.
References: 1: PMBOK Guide, 7th edition, Chapter 4: Keeping the Team on Track, Section 4.4: Manage Issues, pp. 104-105 2: PMBOK Guide, 7th edition, Chapter 4: Keeping the Team on Track, Section 4.4.2: Manage Issues: Outputs, pp. 106-107 : PMBOK Guide, 7th edition, Chapter 4: Keeping the Team on Track, Section 4.5: Capture Knowledge, pp. 108-109 : PMBOK Guide, 7th edition, Chapter 4: Keeping the Team on Track, Section 4.5.2: Capture Knowledge: Outputs, p. 110 : PMBOK Guide, 7th edition, Chapter 2: Creating a High-Performing Team, Section 2.4: Engage Stakeholders, pp. 42-43 : PMBOK Guide, 7th edition, Chapter 2: Creating a High-Performing Team, Section 2.4.2: Engage Stakeholders: Outputs, p. 44 : PMBOK Guide, 7th edition, Chapter 3: Doing the Work, Section 3.4: Navigate Uncertainty and Ambiguity, pp. 72-73 : PMBOK Guide, 7th edition, Chapter 3: Doing the Work, Section 3.4.2: Navigate Uncertainty and Ambiguity: Outputs, p. 74
Submit