CompTIA Project+ PK0-005 (PK0-005) — Questions 451–525

Gold plating is when the project team adds extra features beyond what was required, which can introduce risk and scope creep.

In a functional organization, the project manager has limited authority and resources are controlled by functional managers, leading to resource availability issues.

A risk matrix is a tool that plots risks on a grid based on their probability of occurrence and potential impact, allowing the project manager to prioritize risks visually. This aligns directly with the question's description of plotting risks by these two dimensions. The risk matrix is a standard tool in project risk management for qualitative risk analysis.

The core issue is a misalignment between the product owner's prioritization and the testing team's need for stable builds. Facilitating a meeting allows the product owner to understand the testing team's constraints (e.g., need for stable, integrated builds) and adjust the backlog to include high-value, testable features. This directly addresses both the sponsor's concern about low-value work and the testing team's complaint, without prematurely escalating or restructuring the project.

The stakeholder register entry indicates the sponsor has high power and high interest in the project. According to the power/interest grid, stakeholders in this quadrant should be 'managed closely' to ensure their expectations are met and they remain engaged. This approach aligns with PMI's stakeholder engagement best practices for key decision-makers.

The project management plan is the formal, approved document that defines how the project is executed, monitored, and controlled. The cost baseline, schedule baseline, and scope baseline are all fundamental components of the project management plan, as they represent the approved versions of the project budget, schedule, and scope against which performance is measured.

RFP (Request for Proposal) and SOW (Statement of Work) are common procurement documents.

Agile approach typically has self-organizing teams, frequent customer feedback, and iterative delivery. Detailed upfront planning is predictive; fixed scope is predictive; PM as servant leader is agile.

The Estimate at Completion (EAC) when current cost performance is expected to continue is calculated using the formula EAC = BAC / CPI. First, calculate the Cost Performance Index (CPI) = EV / AC = $90,000 / $100,000 = 0.9. Then, EAC = $200,000 / 0.9 = $222,222.22, which rounds to $222,222.

Mandatory dependencies (hard logic) are inherent to the work, like physical requirements.

A digital Kanban tool that can be displayed on a screen for stand-ups and accessed remotely satisfies both requirements: it maintains the visual board for daily stand-ups (via a large monitor) and provides digital access for remote members. This approach eliminates the synchronization problem entirely because there is only one board—the digital one—that is always up to date, unlike a physical board that would require manual replication. Tools like Jira, Trello, or Azure Boards offer real-time updates and can be projected, making them ideal for hybrid Agile teams.

The project charter is created during the Initiating phase to formally authorize the project.

Predictive (waterfall) is best for projects with stable, well-understood requirements. Agile is for evolving requirements, and hybrid combines both. Scrum is an agile framework.

Agile is the correct methodology because it is designed for projects with high uncertainty and rapidly changing requirements. It emphasizes iterative development, frequent delivery of value, and adaptive planning, which directly addresses the sponsor's concerns about cost overruns by allowing the team to adjust scope and priorities based on feedback.

Norming is when team members start to resolve differences and agree on norms.

The scope baseline and schedule baseline are formal, approved components of the project management plan. The scope baseline consists of the scope statement, Work Breakdown Structure (WBS), and WBS dictionary, while the schedule baseline is the approved version of the project schedule. Both are essential for measuring and controlling project performance.

EMV = Probability × Impact = 0.3 × $50,000 = $15,000.

The WBS is created, and the lowest level is a work package.

Risk response strategies include avoid, transfer, mitigate, and accept. Exploit is a positive risk response strategy.

Analogous estimation uses historical data from similar projects as a basis for estimation.

Burndown chart shows remaining work over time in a sprint, and burnup chart shows completed work over time. Velocity is a metric across sprints, not within one sprint; product backlog and Kanban board are not metrics.

In the storming stage, team members may have conflicts and disagreements as they assert their opinions and struggle for positions. This is a natural part of team development.

The project management plan includes baselines (scope, schedule, cost) and subsidiary management plans. The risk register, issue log, and stakeholder register are project documents.

Agile methodologies are designed to handle evolving requirements and frequent changes.

The 100% rule ensures that the WBS includes all the work required to complete the project scope, and nothing outside it.

A RACI matrix defines roles and responsibilities for each task or deliverable using the four categories.

Earned value management (EVM) is the correct technique because it integrates scope, schedule, and cost data to provide objective performance metrics (e.g., Cost Performance Index, Schedule Performance Index) that allow the project manager to continuously monitor and control expenses against the approved budget. For a firewall upgrade with multiple branch offices, EVM helps detect cost overruns early by comparing planned value (PV), earned value (EV), and actual cost (AC), enabling corrective actions before the tight budget is exceeded.

Predictive (waterfall) works best when requirements are stable and phases are sequential.

The scope statement defines the project scope including deliverables, acceptance criteria, exclusions, assumptions, and constraints.

A Pareto chart displays causes in descending order of frequency, applying the 80/20 rule to focus on the most significant issues.

The work breakdown structure (WBS) is a deliverable-oriented decomposition of the project scope into smaller, manageable components, providing a common framework for scope definition and control. The scope statement formally documents the project scope, including deliverables, assumptions, and constraints, serving as the baseline against which scope changes are evaluated. Both documents are essential for establishing and maintaining scope boundaries throughout the project lifecycle.

When the critical path is extended, the first action is to analyze the impact on the project end date to understand the severity of the delay before deciding on corrective actions. This aligns with the PMBOK Guide's 'Control Schedule' process, where the project manager must assess variance and its effect on the project baseline. Without this analysis, any subsequent action like crashing or fast-tracking may be premature or misdirected.

The risk register is created during the project planning phase to identify, assess, and document potential risks that could impact the project. It includes risk descriptions, probability, impact, and response strategies, forming a key input for risk management throughout the project lifecycle.

In a functional organization, the project manager's role is primarily that of a coordinator or expediter, with limited authority over project resources and team members. Functional managers retain authority over personnel and budget, leaving the project manager to facilitate communication and track progress without direct control.

SV = EV - PV = -$5,000 (behind schedule). CV = EV - AC = -$10,000 (over budget). CPI = EV/AC = 0.818, SPI = EV/PV = 0.9.

A negative cost variance (CV) of -$5,000 means the project has spent $5,000 more than the value of work performed, indicating a cost overrun. A cost performance index (CPI) of 0.9 confirms that for every dollar spent, only $0.90 of earned value is being received, which is a clear sign of being over budget. Therefore, the project is over budget, making option B correct.

The 100% rule states that the WBS must capture all work defined in the project scope, ensuring nothing is left out.

Initiation typically produces the project charter, stakeholder register, and kickoff meeting minutes. Scope statement and risk register are planning outputs.

The Request for Proposal (RFP) is a key document in the project procurement management process, as it formally solicits bids from vendors for goods or services. It defines the project requirements and evaluation criteria, enabling a structured procurement process. The RFP is created after the procurement management plan and is essential for vendor selection.

The hypervisor management console (e.g., vCenter for VMware or Hyper-V Manager) provides built-in performance monitoring and historical data collection for virtualized servers, allowing the team to baseline CPU and memory usage directly from the virtualization layer. This is the correct tool because it captures resource utilization at the hypervisor level, which is essential for establishing performance baselines in a virtualized environment.

Mitigation reduces the probability or impact of a threat.

Current CPI = EV/AC = 120,000/130,000 = 0.9231. EAC = BAC/CPI = 200,000 / 0.9231 ≈ $216,667. Alternatively, EAC = AC + (BAC - EV)/CPI = 130,000 + (80,000)/0.9231 ≈ $216,667.

The Schedule Performance Index (SPI) is calculated as EV / PV. With EV = $500 and PV = $600, SPI = 500 / 600 = 0.8333, which rounds to 0.83. An SPI less than 1.0 indicates the project is behind schedule because less value has been earned than planned.

Stakeholders with high power and high interest should be managed closely as they have significant influence and are highly interested in the project's outcome.

The project charter is the document that formally authorizes a project and provides the project manager with authority to apply organizational resources.

A negative schedule variance (SV = EV - PV) indicates that the earned value (EV) is less than the planned value (PV), meaning the project is behind schedule. In this case, SV = -$5,000 confirms the project has accomplished less work than planned at the measurement date.

The product backlog is an ordered list of everything that is known to be needed in the product.

The project sponsor provides resources, champions the project, and resolves escalations. The PM plans and executes; the team does tasks; the steering committee provides governance.

A change control process is the formal mechanism to evaluate, approve, or reject changes to project scope. By requiring all feature requests to go through this process, the project manager ensures that scope creep is prevented because no minor feature can be added without documented approval and impact analysis. This directly addresses the root cause—stakeholders bypassing formal approval.

Establishing a change control board (CCB) during the planning phase provides a formal, documented process for reviewing and approving or rejecting scope changes. This prevents uncontrolled scope creep by ensuring that any change request is evaluated for impact on cost, schedule, and resources before implementation, which is a key practice in the PMBOK Guide for the execution phase.

The cost performance index (CPI) is calculated as EV divided by AC. With EV = $50,000 and AC = $60,000, CPI = 50,000 / 60,000 = 0.8333, which rounds to 0.83. A CPI less than 1.0 indicates the project is over budget, as each dollar of work completed costs more than planned.

A point above the UCL indicates a special cause variation, which requires investigation to identify and address the root cause.

The project manager must first initiate a formal change request to assess the impact of the new feature on cost, schedule, and resources before any action is taken. This aligns with the PMI's integrated change control process, which requires evaluating trade-offs in a software development context where code dependencies and integration points can be affected. Adding features without analysis risks scope creep, budget overruns, and missed deadlines.

Closing phase includes final acceptance, handover, and release of resources. Initiating starts the project; planning plans; executing does the work.

Hybrid combines predictive (waterfall) for stable parts and agile for iterative parts.

In Scrum, the product owner manages the product backlog and prioritizes work. The project manager (or Scrum Master) facilitates the process but the product owner owns priority decisions.

The lowest level of a work breakdown structure (WBS) is the work package, which represents the smallest unit of work that can be reliably estimated, assigned, and managed. Decomposing deliverables into work packages enables precise cost, resource, and schedule planning during the project planning phase.

A project is a temporary endeavor with a defined beginning and end, specific scope, budget, and schedule. A program is a group of related projects, and a portfolio is a collection of projects or programs aligned to strategic objectives.

EAC = BAC / CPI. CPI = EV/AC = $120,000/$150,000 = 0.8. Thus, EAC = $200,000 / 0.8 = $250,000.

Optimizing cloud resource usage and eliminating waste directly addresses the root cause of the budget overrun—higher-than-expected cloud service costs—without requiring additional funds, scope reduction, or deadline extension. By right-sizing instances, leveraging reserved instances, or terminating idle resources, the project manager can reduce ongoing costs while maintaining the migration schedule. This aligns with cloud cost management best practices and keeps the project within the fixed budget.

The project management plan contains subsidiary plans, including scope, schedule, cost, quality, etc. The project charter and WBS are separate documents.

Hybrid combines predictive for overall plan and agile for flexible parts. Predictive would be too rigid; agile lacks upfront plan; iterative may not suit construction.

The network configuration shows two interfaces, likely representing a dual-homed or multi-homed setup. Without a redundancy protocol such as HSRP, VRRP, or GLBP, there is no automatic failover for the default gateway, meaning a single link or router failure would cause a loss of connectivity for the branch office. This is a project management concern because it impacts network availability and business continuity, which should be addressed in the project requirements.

Using an unauthorized software library with a license that creates legal risks must be stopped immediately to protect the company from potential litigation. The project manager must then assess the schedule impact and develop a replacement plan, as continuing use without addressing the legal risk violates compliance and project governance standards.

Proposal A has an NPV of $150,000, which is a direct measure of the project's value creation in today's dollars. Since NPV accounts for the time value of money and the organization's cost of capital (10%), a positive NPV indicates the project is expected to generate value above the required return. Among the options, NPV is the most financially sound criterion because it quantifies absolute wealth increase, unlike payback period (which ignores time value and cash flows after payback) or IRR (which can be misleading for mutually exclusive projects).

Resource constraints refer to limited availability of personnel, equipment, or materials. This scenario describes a resource constraint due to limited availability of a key person.

The scope baseline is a component of the project management plan because it formally defines the project's scope, deliverables, and acceptance criteria. It consists of the scope statement, Work Breakdown Structure (WBS), and WBS dictionary, which together establish the foundation for scope control and validation throughout the project.

The Gantt chart is the correct tool because it visually represents a project schedule with horizontal bars plotted against a timeline, where each bar corresponds to a task, and it can display dependencies (via arrows or linking lines) and milestones (as diamond symbols). This aligns directly with the description in the question, making it the standard choice for schedule visualization in project management.

A CPI of 0.8 means the project is earning only $0.80 for every $1.00 spent, indicating cost overrun (over budget). An SPI of 1.1 means the project is earning $1.10 for every $1.00 of planned work, indicating progress ahead of schedule. Therefore, the project is over budget and ahead of schedule, making option B correct.