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

In response to new legislation requiring the release of contractors or their conversion to full-time employees, the project manager should prioritize compliance with the law. This may involve using only full-time employees, even if it results in project delays. The focus should be on legal compliance and the ethical treatment of workers, rather than solely on project timelines.

References = The answer is based on standard project management practices and the typical response to changes in legislation affecting project staffing. For detailed information, please refer to the CompTIA Project+ Study Guide and other official CompTIA resources.

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.

Kanban is a visual workflow management method that aims to maximize efficiency and promote continuous improvement by visualizing work, limiting work in progress, and enhancing flow.

The CompTIA Project+ PK0-005 exam objectives, under Domain 1.1: Explain the basic characteristics of a project and various methodologies and frameworks used in IT projects, include Kanban as a methodology:

"Methodologies and frameworks: Kanban."

CompTIA Project+ PK0-005 Exam Objectives

Kanban helps teams manage work by visualizing tasks and optimizing the flow from start to finish, aligning with the principles of efficiency and continuous improvement.

The process is out of control and should be revised. The project manager can use the rule of seven to determine the status of the process based on the control chart. The rule of seven states that if seven or more consecutive measurements fall on one side of the mean that there’s an assignable cause that needs investigation. In this case, the last seven data points are all below the mean, which indicates that the process is out of control and in need of adjustment12

 Review the resource pool and review the project objectives are activities that the project manager should undertake after accepting a new project. Reviewing the resource pool involves identifying and evaluating the availability, skills, and competencies of the human and material resources that are needed for the project. Reviewing the project objectives involves understanding and clarifying the expected outcomes and benefits of the project and how they align with the organizational strategy and stakeholder expectations. These activities can help to plan and execute the project effectively and efficiently.

A project manager who makes a company-wide announcement about the successful completion of a project and thanks team members is doing the following:

Celebrating the team’s hard work: This is the correct answer, as the project manager is acknowledging the efforts and contributions of the team members and showing appreciation and recognition for their performance12.

Bringing attention to the project sponsor: This is not the correct answer, as the project manager is not highlighting the role or involvement of the project sponsor, who is the person who provides the resources and authority for the project.

Sharing lessons learned: This is not the correct answer, as the project manager is not discussing the successes, challenges, or best practices of the project, which are part of the lessons learned process.

Collecting feedback: This is not the correct answer, as the project manager is not soliciting any input or opinions from the team members or other stakeholders, which are part of the feedback process.

Part 1:

Change Control Process:

Consult the RACI matrix.

Define new requirements and record changes.

Assess the schedule, risk, and cost.

Perform a demonstration.

Obtain a sign off.

Update and test the deliverable.

Make an announcement on the company portal.

The change control process is a sequence of steps that helps to manage and document any changes or modifications to a project scope, schedule, cost, quality, or resources. The change control process typically involves the following steps:

Consult the RACI matrix. A RACI matrix is a tool that defines and clarifies the roles and responsibilities of each team member for each task or activity in a project. RACI stands for responsible, accountable, consulted, and informed. Consulting the RACI matrix can help to identify who needs to be involved or informed about the change request and how to communicate with them.

Define new requirements and record changes. The new requirements and changes are the details of what needs to be modified or added to the project deliverables or objectives based on the customer feedback or request. Defining and recording the new requirements and changes can help to communicate and justify the need and rationale for the change and its implications on the project scope and quality.

Assess the schedule, risk, and cost. The schedule, risk, and cost are the aspects of the project that may be affected by the change request. Assessing the schedule, risk, and cost can help to determine the impact and feasibility of the change and identify any possible alternatives or corrective actions to minimize or avoid its negative effects.

Perform a demonstration. A demonstration is a presentation or show of how the modified or updated deliverable works or meets the customer expectations or requirements. Performing a demonstration can help to validate and verify that the change request has been implemented correctly and effectively and to obtain feedback or approval from the customer or stakeholders.

Obtain a sign off. A sign off is a formal acceptance and approval of the change request and its deliverables from the customer or stakeholders. Obtaining a sign off can help to confirm that the change request has been completed successfully and satisfactorily and to close the change control process.

Update and test the deliverable. The deliverable is the product or service that is produced or provided by the project. Updating and testing the deliverable can help to ensure that it meets the quality standards and criteria and that it works as expected after implementing the change request.

Make an announcement on the company portal. The company portal is a platform or channel that allows internal communication and collaboration among employees within an organization. Making an announcement on the company portal can help to inform and update other team members or departments about the change request and its outcomes and to share any lessons learned or best practices from the change control process.

Part2:

Risk register: A risk register is a document that identifies, analyzes, and records the potential risks or uncertainties that may affect a project. Updating the risk register can help to capture any new or modified risks that may arise from the change request and to plan and implement appropriate risk responses.

Schedule: A schedule is a document that shows the planned start and end dates, durations, dependencies, and progress of each task or activity in a project. Updating the schedule can help to reflect any changes or adjustments to the project timeline or milestones that may result from the change request and to monitor and control the project performance and delivery.

Statement of work: A statement of work (SOW) is a document that defines the scope, deliverables, schedule, and terms and conditions of a project or contract. Updating the SOW can help to document any changes or additions to the project scope or deliverables that may be requested or agreed upon by the customer or stakeholders and to ensure alignment and agreement on what needs to be done and how it will be done.

Change log: A change log is a document that tracks and records any changes or modifications that are made to the project scope, schedule, cost, quality, or resources during a project. Updating the change log can help to document the change request, approval, implementation, and impact of each change and ensure traceability and transparency.

The critical path of the project is the longest sequence of tasks that must be completed on time for the project to finish on schedule. It determines the shortest possible duration of the project and shows the tasks that have no slack or float. Any delay in the critical path tasks will affect the project completion date. To find the critical path, we need to calculate the earliest start (ES), earliest finish (EF), latest start (LS), latest finish (LF), and slack (S) for each task. We can use the table and the network diagram given in the question to do this. The formula for calculating the slack is S = LF - EF or S = LS - ES. A task with zero slack is on the critical path. The calculations are as follows:

Task | Duration | ES | EF | LS | LF | S A | 10 | 0 | 10 | 0 | 10 | 0 B | 15 | 10 | 25 | 10 | 25 | 0 C | 10 | 10 | 20 | 15 | 25 | 5 D | 20 | 25 | 45 | 25 | 45 | 0 E | 10 | 25 | 35 | 35 | 45 | 10 F | 15 | 20 | 35 | 30 | 45 | 10 G | 5 | 45 | 50 | 45 | 50 | 0 H | 10 | 35 | 45 | 40 | 50 | 5 I | 20 | 35 | 55 | 30 | 50 | -5 J | 5 | 50 | 55 | 50 | 55 | 0

Based on the table, we can see that the tasks with zero slack are A, B, D, G, and J. Therefore, the critical path is A-B-D-G-J, which has a total duration of 55 days. The other options are not the correct critical paths, as they either include tasks with positive slack (such as C, E, F, and H) or have a longer duration than 55 days (such as A-C-F-I-J).

Scrum is an agile methodology well-suited for projects that require frequent milestone deliveries and functionality demonstrations. It emphasizes iterative development, with regular presentations to stakeholders, which aligns with CompTIA Project+ principles for agile project management.