CompTIA PK0-005 - CompTIA Project+ Certification (2025)

The project manager should communicate the change deployment next after updating the project plan with the newest project end date as a result of an approved change. Communicating the change deployment involves informing all relevant parties about when and how the change will be implemented and what are the expected outcomes and benefits. Communicating the change deployment can help to ensure alignment, readiness, and support for the change and avoid any confusion or resistance.

The project manager and team should review assumptions and constraints for input to the risk register during the planning phase of a project. Assumptions are statements that are considered to be true for the purpose of planning, but may or may not be valid in reality. Constraints are factors that limit the project scope, time, cost, quality, or resources. Both assumptions and constraints can introduce risks to the project, which are uncertain events or conditions that can have a positive or negative impact on the project objectives. The risk register is a document that records the identified risks, their causes, impacts, probabilities, responses, owners, and status. Reviewing assumptions and constraints can help the project manager and team identify, analyze, prioritize, and plan for the potential risks that may affect the project12.

The other options are not the correct activities that the team should do during the planning phase of a project. Identifying and assessing stakeholders (option A) is an activity that is done during the initiating phase of a project, not the planning phase. Stakeholders are individuals or groups that have an interest or influence in the project, and their identification and assessment is important to define the project scope, objectives, and success criteria, and to establish a communication plan12. Holding daily status meetings (option B) is an activity that is done during the executing and monitoring and controlling phases of a project, not the planning phase. Daily status meetings are short and frequent meetings where the project team members report on their progress, issues, and plans for the next day. Daily status meetings can help the project manager track the project performance, resolve problems, and communicate updates12. Removing access and planning the project sign-off (option C) is an activity that is done during the closing phase of a project, not the planning phase. Removing access is a security measure to ensure that the project resources do not have access to the project systems, data, or assets after the project is completed. Planning the project sign-off is a process to obtain the formal acceptance and approval of the project deliverables from the stakeholders and customers12.

Agile methodologies emphasize flexibility and iterative progress, so strict deadlines can be a concern. They may limit the team’s ability to adapt and respond to change, as emphasized by CompTIA Project+ in agile project management principles.

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. References: CompTIA Project+ Study Guide, Chapter 3: Project Integration Management, Objective 3.1: Identify the project management processes and the interactions between them.

Preliminary procurement involves identifying and evaluating potential vendors based on their qualifications and capabilities. This step is essential for project procurement and aligns with CompTIA Project+ best practices for vendor selection.