According to the PMBOKGuide, 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: PMBOKGuide, 7th edition, page 101 2: PMBOKGuide, 7th edition, page 113

When data breaches continue to occur despite training, it indicates that there may be underlying issues that are not being addressed by the current measures. In such cases, the project manager should apply a root-cause analysis to identify the underlying causes of the data breaches. This could involve engaging a team of forensic experts to conduct a thorough analysis of the incidents12. The root-cause analysis will help to identify whether the breaches are due to technical vulnerabilities, procedural issues, or human factors. Once the root causes are identified, appropriate measures can be taken to address them. This could involve changes to systems, processes, or further training1234. References: What Should Companies Do After a Data Breach? | UpGuard1; 6 Steps to Developing a Data Breach Response Plan - Spectral2; Data Breach Response: A Guide for Business - Federal Trade Commission3; What Is a Data Breach? Best Practices and Fixes for Businesses - G2

Engaging with the community and keeping them informed is a key aspect of project management, especially for projects that directly affect local community members. Regular community meetings are an effective way to share updates, gather feedback, and ensure that the community's needs and concerns are being addressed.
This approach aligns with best practices in community engagement, which emphasize the importance of transparency, inclusivity, and active participation in the decision-making process.
: = The information provided is based on best practices in community engagement and communication as outlined in resources related to Project Management Professional (PMP) and Professional in Business Analysis (PMI-PBA) standards12345. These resources highlight the importance of regular communication and involvement of community members in projects that impact them.

In an agile project, when there is a disagreement about a major new requirement among key stakeholders, the project manager should facilitate a meeting with the stakeholders and product owner to clarify the new need.
This approach ensures that all parties have a clear understanding of the requirement and can work towards a common goal. It also helps to prevent potential issues that could arise from misunderstandings or miscommunications. References: PMBOKGuide - Sixth Edition, Section 13.2.2.1: Plan Stakeholder Engagement

On day four of a 15-day sprint, the team should continue with the sprint work as planned and keep monitoring the burndown chart. The burndown chart is a visual representation of the work left versus the time remaining in the sprint. If the "Actual" line closely follows the "Planned" line, it indicates that the team is on track. Making adjustments or changing the sprint scope at this stage is premature unless there are significant deviations or impediments1. The team should maintain their current pace and monitor progress, making adjustments only if necessary as the sprint progresses2. References: "Burndown Chart: What it is, How to Use it, Example [2024]" by Asana; "Scrum Sprint Burndown Chart [Everything you Need to Know] " by KnowledgeHut12.