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

The program manager should schedule a call with the vendor PM and vendor executive to review the statement of work (SOW), which is a document that defines the scope, deliverables, timeline, quality, and payment terms of the project. The program manager should clarify the expectations and criteria for user acceptance testing (UAT), which is a process of verifying that the system meets the user’s requirements and expectations. The program manager should also discuss the reasons for the UAT failure and the corrective actions needed to resolve the issues. The program manager should not approve the invoice until the UAT is successfully completed, as this would compromise the quality and value of the project. The program manager should also not escalate the issue or work on a compromise without first reviewing the SOW and communicating with the vendor12.

The sponsor wants the document where the initial scope is defined, and the best place to confirm that baseline is the project charter. The charter authorizes the project and typically includes the high-level purpose, objectives, high-level scope, key stakeholders, and success criteria. CompTIA Project+ emphasizes reviewing and using existing project artifacts to maintain alignment; when a stakeholder’s view of scope differs, the PM should first reference the authoritative initiation artifact that establishes the original agreement.

Creating a new project management plan (A) is premature and could worsen confusion if the baseline is not reconfirmed. Meeting minutes (B) can provide context, but they are not the formal scope authorization document the sponsor is asking for. “Perform project scope management” (C) is important as an ongoing process, but the question is asking what to do next to clarify differences and provide the initial scope document—reviewing the charter is the fastest and most correct step.

After reviewing the charter, the PM can facilitate alignment with the new stakeholder, and if scope truly needs to change, route it through formal change control and update scope artifacts accordingly.

A Finish-to-Start dependency implies that a subsequent activity cannot start until a previous one finishes. In this scenario, the manufacturing process (subsequent activity) cannot begin until the critical raw materials (previous activity) have been delivered. This type of dependency is the most common in project schedules and is likely being affected by the global shipping slowdown, causing delays in the start of the project ' s production run.

A milestone chart is a tool that shows the key events or deliverables of a project along a timeline12. A milestone chart is useful for tracking the progress of a project that has technical tasks and requires a SME’s knowledge, because it can provide a high-level overview of the project status, without getting into the details of each task or activity34. A milestone chart can help the PM and the project lead communicate the project achievements, challenges, and expectations to the stakeholders, and also identify any potential risks or delays that may affect the project completion56. A milestone chart is better than the other options because:

A Gantt chart is a tool that shows the tasks, dependencies, durations, and resources of a project along a timeline7. A Gantt chart is more detailed and complex than a milestone chart, and may not be suitable for providing high-level updates to the stakeholders8.

A project organization chart is a tool that shows the roles, responsibilities, and reporting relationships of the project team members and other stakeholders9. A project organization chart is not a tool for tracking project data, but rather for defining the project structure and authority10.

A Program Evaluation Review Technique (PERT) chart is a tool that shows the tasks, dependencies, and critical path of a project along a network diagram. A PERT chart is more focused on the sequence and timing of the project tasks, and may not capture the key milestones or deliverables of the project.

References = CompTIA Project+ Certification Study Guide, CompTIA Project+ Certification Exam Objectives, What is a Milestone Chart?1, How to Create a Milestone Chart in Excel in 3 Steps2, Milestone Chart: The Easiest Way to Track Project Milestones3, How to Use Milestones in Project Management4, What is a Gantt Chart?5, Gantt Chart vs Milestone Chart: What’s the Difference?6, What is a Project Organization Chart?7, How to Create a Project Organization Chart8, What is a PERT Chart?9, PERT Chart vs Gantt Chart: What’s the Difference?10

A risk log or risk register is used to document potential risks to the project, including the loss of team members due to high stress. CompTIA Project+ recommends this log as a tool for identifying and managing risks throughout the project lifecycle.

One of the primary purposes of a stand-up meeting is to identify blocking tasks that hinder progress. This allows the team to address issues promptly and maintain momentum.

In the CompTIA Project+ PK0-005 exam objectives, under Domain 1.8: Compare and contrast communication management concepts, stand-up meetings are highlighted as a tool for daily communication to surface impediments and coordinate efforts.

The Work Breakdown Structure (WBS) is a hierarchical decomposition of the total scope of work to accomplish project objectives. If tasks can be broken into smaller deliverables, the WBS should be updated first to reflect these changes.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 2.2: Given a scenario, determine the appropriate scope management activities, maintaining an accurate WBS is crucial for effective scope management.

An Informative meeting is designed to share information, such as presenting new software features to stakeholders. This type of meeting ensures that all participants are informed about the software ' s capabilities and how it will impact their work.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 1.8: Compare and contrast communication management concepts, recognizing different meeting types, including informative meetings, is essential for effective communication management.