Explanation
The project manager should use a Pareto chart to prioritize which defects to address for the product. A Pareto chart is a type of bar chart that shows the frequency or impact of different causes of problems or defects. It also shows a cumulative line that represents the percentage of the total frequency or impact. A Pareto chart can help to prioritize the causes that have the most significant effect on the quality of the product and apply the
80/20 rule, which states that 80% of the problems are caused by 20% of the causes.

Explanation
The Pareto chart should be used to identify the most important causes of issues during a quality analysis review. The Pareto chart is a graphical representation of the frequency and impact of different causes, helping to identify the most common and impactful causes. References: CompTIA Project+ Study Guide Section 3.3.3

The project manager should communicate with the affected stakeholders first after realizing that the sign-off
for the project scope baseline is delayed due to multiple changes and that the budget for this project is
restricted by the project sponsor. The affected stakeholders are those who have an interest or influence on the
project and may be impacted by any changes or delays. Communicating with them can help to explain the
situation, assess the impact, seek feedback, and manage expectations.

The next step after defining tasks, durations, resources, and costs is to establish baselines. A baseline is an approved version of a project plan that serves as a reference point for measuring progress and performance throughout the project lifecycle. A baseline typically includes scope, schedule, cost, quality, and risk parameters. Establishing baselines involves presenting the project plan to key stakeholders and obtaining their formal agreement on the project objectives and deliverables. Baseline approval can help to establish clear expectations, avoid scope creep, and facilitate change control during project execution34

An issue log is a tool that records and tracks any issues that arise during the project. It helps the project
manager to identify, prioritize, assign, monitor, and resolve the issues in a timely manner. An issue log can
also include information such as the issue description, impact, status, owner, and resolution date1. An issue log
is different from a defect log, which records and tracks the defects or errors in the project deliverables. A risk
register is a tool that records and tracks the potential risks that may affect the project objectives. A change log
is a tool that records and tracks the changes that are made to the project scope, schedule, budget, or quality2.