An Ishikawa diagram, also known as a fishbone diagram, is a tool used to identify and analyze the root causes of a particular problem. CompTIA Project+ references this tool as essential for quality management and problem-solving.

The dependency between software installation and desktop installation is a mandatory dependency. A mandatory dependency is a type of dependency that is inherent in the nature or logic of the work and cannot be avoided or changed. It is also known as a hard dependency or a hard logic dependency. A mandatory dependency means that one task must be completed before another task can start or finish. For example, software installation can only start after desktop installation is finished5 The dependency between desktop installation and software installation represents a mandatory dependency. A mandatory dependency is a type of task dependency that is inherent in the nature of the work being performed. In this case, software installation cannot begin until desktops are installed and powered on, and therefore, the dependency is mandatory. Reference: CompTIA Project+ Study Guide, Chapter 3: Project Integration Management, Objective 3.1: Identify the project management processes and the interactions between them.

The project manager should address the issue of damage to the monitor first because it has the highest
percentage (40%) among the issues observed. This means that it is the most frequent and severe issue that
affects the quality and functionality of the refurbished desktops. Addressing this issue first can help to improve
customer satisfaction, reduce rework, and avoid waste1

A strategy to store records must include data management and document management as two essential
elements. Data management is the process of ensuring that the data collected, stored, and used by the project is
accurate, complete, consistent, secure, and accessible. Data management helps to maintain the quality and
integrity of the project data and supports the analysis and reporting of the project outcomes1, p. 4
Document management is the process of creating, organizing, storing, retrieving, and disposing of project
documents in a systematic and controlled way. Document management helps to ensure that the project
documents are available, reliable, usable, and authentic throughout the project life cycle and
beyond. Document management also helps to comply with the legal, regulatory, and organizational
requirements for records retention and disposition2, p. 3

Transfer is a risk management strategy that involves shifting the responsibility or impact of a risk to a third
party, such as an insurance company, a vendor, or a contractor1. By buying an extended warranty for a set of
servers, the project manager is transferring the risk of server failure or malfunction to the warranty provider,
who will cover the cost of repair or replacement in case of a risk event. This way, the project manager reduces
the exposure and liability of the project to the risk, while still retaining some level of accountability and
oversight2. References = CompTIA Project+ PK0-005 Certification Study Guide, Chapter 8: Planning Projects
Part 4, page 245; 4 Risk Management Strategies for Successful Project Execution, Risk transferring
section; How to Manage Project Risk: A 5-Step Guide, Risk treatment section.