CompTIA Project+ PK0-005 (PK0-005) — Questions 751–825

A negative NPV means the project's discounted future cash inflows are worth less than the initial investment, destroying value. Rejecting it is the financially sound recommendation, satisfying the stem's constraint that the sponsor act on the -$15,000 figure.

Task A starting after Task B finishes is finish-to-start; Task C completing before Task D starts is also finish-to-start; Task E starting when Task F starts is start-to-start. The sequence therefore reads FS, FS, SS.

Dividing BAC by CPI gives the EAC when current cost performance persists: CPI is $100,000 ÷ $120,000 = 0.833, so $200,000 ÷ 0.833 ≈ $240,000. This satisfies the stem's constraint that the existing CPI continues unchanged.

Assessing the change's impact on scope, schedule, cost and risk must precede any approval decision or baseline update. This satisfies the stem's requirement to act first, ensuring the change control board receives evidence before authorising or rejecting the request.

Archiving project documents preserves the historical record, lessons learned and audit evidence after closure. It is a recognised closing activity because it secures artefacts for future reference and compliance, satisfying the stem's requirement for activities typically performed during project closing.

The Delphi technique uses iterative rounds of anonymous questionnaires, letting experts revise answers after seeing the aggregated group response. This directly satisfies the stem's constraints: anonymity, facilitator aggregation, and revision. Unlike brainstorming or nominal group technique, Delphi removes face-to-face pressure, converging expert opinion without direct confrontation.

The project charter formally authorises the project and documents its high-level scope, objectives, and key stakeholders. It is the initiating document the sponsor approves, whereas subsidiary plans and the scope statement contain far greater detail.

The project manager should first address the team directly to understand the root cause and reinforce expectations. A meeting allows for open communication, clarification of standards, and identification of any training gaps. This aligns with the Executing phase's focus on team development and quality assurance. If the issue persists, more formal actions like process adjustments or performance management can follow.

Once a risk is identified during planning, it must be documented in the risk register with a planned response before further action. Capturing the supplier risk and defining a response is the immediate next step, enabling later analysis and monitoring.

The work breakdown structure decomposes the total project scope into deliverable-oriented, manageable components, providing the definitive hierarchical scope baseline. It satisfies the stem's scope-definition requirement, complementing the scope statement by translating agreed deliverables into discrete work packages for estimation and control.

Historical velocity of 30 story points is the team's demonstrated capacity per sprint. Committing to 35 exceeds that proven throughput, so committing to 30 aligns the sprint commitment with actual delivery data rather than the product owner's aspiration.

Formal acceptance is the closing process where the customer or sponsor signs off that deliverables satisfy documented requirements, converting provisional output into accepted product. It directly satisfies the stem's demand for obtaining formal acceptance during project closing.

A RACI chart maps each task to who is Responsible, Accountable, Consulted and Informed, directly resolving ambiguity over task assignments. It is the artefact that clarifies roles and responsibilities, satisfying the stem's need to settle conflicts about who does what.

Net Present Value discounts all future cash flows to today's value, directly satisfying the steering committee's requirement to maximise return over time. Unlike payback period, which ignores cash flows beyond the break-even point, NPV captures total long-term profitability across each project's full lifespan, making it the definitive metric for comparing financial viability.

A Gantt chart plots tasks as horizontal bars against a calendar timeline, with dependency links between bars and critical path activities highlighted. It satisfies all three stem requirements: timeline bars, dependencies, and critical path emphasis.

Closing is the process group where the project manager obtains formal sign-off that deliverables meet acceptance criteria, then archives project documentation and releases resources. It directly satisfies the stem's requirement for formal acceptance and document archiving, which no other process group performs.

SPI is calculated as EV divided by PV, so $120,000 ÷ $150,000 = 0.8. This is the earned value formula applied directly to the stem's figures, confirming the schedule efficiency ratio stated in the option.

Assigning selected team members to activities and verifying their availability is part of Acquire Resources. Once negotiations succeed, the project manager records the assignment against the schedule and confirms that the individuals can support the planned dates. This finalizes the acquisition step for the scarce skill set and is distinct from the planning activities that precede it.

A constraint is a limiting factor that restricts the project team's options, such as a fixed budget, a hard deadline, or a mandated change freeze. The production change freeze is an externally imposed restriction on when migration activities can occur, so it directly limits scheduling options. CompTIA Project+ treats such imposed limitations as constraints that must be documented and factored into the schedule and risk planning.

The project charter is the document that formally authorizes the existence of a project and grants the project manager the authority to apply organizational resources to project activities. It is typically issued by the sponsor or a senior manager. Without a charter, the project manager lacks formal authority, and the project may not be recognized as legitimate within the organization.

A mandatory dependency is one required by the nature of the work itself, such as concrete curing before walls rise. It is inherent to the physical or contractual logic and cannot be altered by the project team.

The Delphi technique uses iterative rounds of anonymous expert questionnaires, with the facilitator summarising responses between rounds. Anonymity removes pressure to conform to dominant voices, satisfying the stem's requirement for unbiased expert input gathered without groupthink before consensus emerges.

Any proposed change must first be captured formally before its cost and schedule impact can be assessed, so the change request form is completed initially. It feeds the subsequent evaluation and approval steps, satisfying the stem's requirement to update the first document when a cost-increasing change is raised.

Controlling quality is a Monitoring and Controlling process that involves monitoring and recording the results of quality activities to assess performance and recommend necessary changes. It ensures that project deliverables meet the required quality standards. This activity is performed throughout the project to identify and correct quality issues, making it a key part of the Monitoring and Controlling process group.

Phase closure verifies that the phase's deliverables met acceptance criteria and that the phase objective was achieved before the next phase begins. Documenting that acceptance, archiving phase records, and capturing lessons learned preserves organizational knowledge and provides the transition basis for the following phase, while leaving ongoing resources in place for continued work.

In a functional organisation, authority rests with functional managers and the project manager acts largely as coordinator, holding minimal power over resources and priorities. This structure therefore gives the project manager the least authority of the options.

The sprint backlog is the subset of product backlog items the team commits to for the sprint, plus the plan for delivering them. It satisfies the stem's constraint of being the resulting list produced during sprint planning, distinct from the product backlog, which holds all unrefined future work.

In an adaptive life cycle, new requirements are welcomed and added to the product backlog. The product owner prioritizes the backlog, and the team pulls items into iterations based on capacity and value. Introducing the requirement mid-iteration would disrupt the team's focus, so the correct action is to add it to the backlog for future consideration. This maintains the iterative process and allows for reprioritization.

Mitigate lowers the probability or impact of a risk, and cross-training directly reduces the impact of losing a key team member by ensuring others can absorb their duties. This satisfies the stem's constraint of reducing impact without eliminating the risk, unlike avoid, transfer or accept strategies.

After submitting the change request, the project manager must evaluate the impact on the triple constraint — scope, schedule and cost — before the change control board can approve, reject or defer it. This assessment informs the subsequent decision step.

Formal acceptance of the final deliverable is the trigger that allows the project to move into closing. Until the customer provides documented sign-off, the project cannot be considered complete, and contractual or payment obligations may remain open. The project manager should secure this acceptance first so that subsequent activities such as archiving, releasing resources, and capturing lessons learned reflect a verified, accepted outcome rather than an unconfirmed one.

Schedule variance is EV minus PV, giving $40,000 minus $50,000, or -$10,000. Cost variance is EV minus AC, giving $40,000 minus $45,000, or -$5,000. Both negative values indicate the project is behind schedule and over budget.

A monthly executive summary aligns with the committee's meeting cadence and provides concise metrics, top risks, and explicit decision requests. This format respects the committee's decision-oriented focus and ensures they receive actionable information at the right frequency, which is exactly what effective communication planning requires for this audience.

Cost variance is EV minus AC: $50,000 − $55,000 = −$5,000. The negative result satisfies the stem's requirement to quantify cost performance, showing the project has overspent by $5,000 against the work completed. PV is irrelevant here, since CV measures actual cost efficiency, not schedule.

The project charter formally authorises the project and names the project manager, satisfying the initiation-phase requirement for documented approval. It also records the high-level scope, budget and timeline the sponsor supplied, distinguishing it from the detailed project management plan, which is produced later during planning.

The project manager should first document the issue and analyze its potential impact on scope, schedule, and stakeholder satisfaction. This systematic approach allows for informed decision-making and helps determine the appropriate response, such as negotiating with the vendor or adjusting the change management process.

Risk response planning develops options and actions to reduce threats and enhance opportunities. The team has a concrete threat, the API deprecation, and is generating and weighing three distinct strategies: avoiding the dependency through a rewrite, transferring or sharing the problem through vendor negotiation, and mitigating by accelerating the cutover. That selection process is exactly risk response planning.

Hybrid suits this construction project because the scope is well-defined yet minor changes remain welcome. Predictive planning locks the baseline schedule and budget, while agile elements absorb small customer adjustments during execution. Pure waterfall would resist those changes; pure agile would waste effort re-planning stable, well-understood work.

Once the CCB approves a change, the project manager must incorporate it into the approved project management plan, updating the affected baselines (scope, schedule, cost) so they reflect the authorised change and remain the reference for measuring future performance.

Because the component is already in production and the defect blocks acceptance, the work required to remediate it must be authorized rather than performed informally. Reopening the project, replanning the affected work, and securing change control board or sponsor approval for the revised baseline restores legitimate control over scope, schedule, and cost. This keeps the project's records accurate and ensures the customer's acceptance decision is based on verified results.

The Statement of Work defines the contractor's specific deliverables, scope, schedule and acceptance criteria for Activity X's specialised skill, establishing exactly what work is performed. It is the document that scopes the engagement before contractual terms are formalised.

A network diagram maps task dependencies and durations, exposing the longest sequential chain through the schedule. This directly satisfies the need to visualise the critical path, since float calculations on that chain reveal which tasks govern the project's completion date. Gantt charts show timing but obscure dependency-driven float.

In a functional organisation, work is grouped by department and the functional manager controls budgets, assignments and priorities. The project manager coordinates across functions with little or no formal authority, giving the least authority over project resources of any structure.

Uncontrolled changes, such as a stakeholder adding unapproved features, constitute scope creep. Because the request bypasses the formal change control process, the project manager cannot assess its effect on the schedule and budget constraints, which is precisely the risk described in the stem.

Developing the project charter is a defining initiation activity: it formally authorises the project and grants the project manager authority to apply organisational resources. This satisfies the stem's initiation-phase constraint, since charter creation and approval occur before planning artefacts such as the schedule, budget baseline or risk register are produced.

The project charter formally authorizes the existence of the project and gives the project manager authority to apply organizational resources to project activities. It is typically issued by the sponsor or initiating entity and includes high-level information such as objectives, success criteria, and the named project manager. This matches the scenario's need for formal authorization.

The work breakdown structure decomposes project deliverables into progressively smaller, manageable components, satisfying the stem's requirement for hierarchical breakdown. Unlike a schedule or charter, the WBS focuses purely on scope decomposition, providing the foundational framework from which tasks, estimates and assignments are later derived.

Frequency of communication specifies how often each stakeholder group receives information, satisfying the plan's need to schedule interactions. It complements details such as method, sender, and audience, ensuring stakeholders know when to expect updates rather than only what will be communicated.

Decomposing scope produces the Work Breakdown Structure, a hierarchical deliverable-oriented decomposition of total project scope. The WBS defines all work required, with lower levels representing progressively finer detail, satisfying the scope-decomposition input. It is not a schedule or activity list; those derive later from the WBS during sequencing and estimation.

Crashing adds resources to critical-path activities, while fast-tracking overlaps sequential activities. Both techniques target the critical path to shorten total duration, so each is a schedule compression method applied when the project is behind schedule.

Overlapping phases via fast-tracking compresses the schedule by starting successor work before predecessors finish, so incomplete deliverables feed forward and defects surface late, forcing rework. This directly addresses the tight-deadline constraint by exposing the schedule-compression trade-off the PM must manage.

EV of $50,000 against PV of $60,000 gives a negative schedule variance, so work lags the plan; EV against AC of $55,000 gives a negative cost variance, meaning spend exceeds earned value. Both indices fall below 1.0, confirming behind schedule and over budget.

Total float of zero means the activity sits on the critical path, so any reduction shortens the whole project. Cutting 5 days from its 15-day duration reduces the 120-day critical path to 115 days, assuming no other path becomes critical.

Payback divides initial investment by annual return: $50,000 ÷ $15,000 = 3.33 years for Project A, versus $80,000 ÷ $22,000 = 3.64 years for Project B. Project A recovers its investment sooner, satisfying the stem's payback criterion.

Ground rules such as meeting etiquette, expected response windows, and channel usage are core team charter content. For a team spread across three time zones, these agreements prevent misunderstandings about availability and set shared expectations for communication. They are established by the team during the forming stage and documented in the charter so behavior is governed by consensus rather than assumption.

Actual cost is the money spent on work performed to date. CPI equals earned value divided by AC, so AC is essential for the cost efficiency calculation; it satisfies the stem's requirement for metrics needed to compute CPI.

The project charter formally authorises the project and records high-level objectives and constraints, giving the project manager authority to proceed. These elements define what the project must achieve and the boundaries within which it must operate.

Purchasing insurance shifts the financial consequence of the risk to a third party rather than eliminating or reducing it. Transfer moves ownership of the impact to an insurer, satisfying the high-probability, high-impact scenario where the team cannot absorb potential losses itself.

The project charter is the initiating document that formally authorises the project, names the project manager, and records high-level objectives, scope, and constraints. It is created during initiation, satisfying the stem's requirement for a document produced in that phase.

Championing the project is a core sponsor responsibility, satisfying the stem's requirement for typical sponsor duties. The sponsor secures executive backing, removes organisational blockers and advocates for resources at senior level, distinct from the project manager's day-to-day delivery duties. This authority-based advocacy is what the scenario's role definition demands.

Regulatory delay requires a formal schedule baseline change; submitting a change request with impact analysis to the change control board is the documented first step. This satisfies the stem by routing the revised schedule through proper approval before communicating or rebaselining.

The risk register records each identified risk alongside its assessed impact and agreed response strategy, which is precisely the content the stakeholders' report requires. It is the only project artefact that pairs risks with impact ratings and planned responses in one maintained document.

Lessons learned captures team feedback on successes and improvement areas as the project closes, matching the stem exactly. It records knowledge for reuse in future projects, distinguishing it from the final report, which summarises performance against baselines, and from the benefits realisation plan, which tracks post-closure value.

Assessing schedule and cost impact before raising the change request satisfies the stem's critical-path constraint. This lets the change control board decide with full data, rather than approving a delay blindly. Documenting impact first is the recognised sequence in change management.

In a fixed-price contract, the price is set, but changes in scope typically require a contract amendment to adjust the price and terms. The CCB approval is an internal step, but the customer must agree to the change and any associated cost. This option correctly reflects that a contract modification is necessary to formalize the change and ensure the seller is compensated for additional work.

When time and cost are constrained, scope is the variable the project manager can most realistically adjust. Working with the sponsor and stakeholders to descope or defer lower-priority features allows the project to meet the regulatory deadline within the capped budget. This is a recognized trade-off approach in the triple constraint and keeps the project aligned with its most critical business objective rather than attempting an impossible delivery.

A program coordinates related projects to obtain benefits not available from managing them individually. This matches the stem's definition, distinguishing it from a portfolio, which groups projects aligned to strategic objectives rather than interdependent ones.

Live migration allows a running virtual machine to be moved from one physical host to another with minimal downtime. This is essential for high availability and maintenance without disrupting services. The project manager should verify that the hypervisor supports this feature, as it directly addresses the requirement to maintain uptime during hardware failures or planned maintenance.

Version control retains every prior revision, so the overwritten charter remains retrievable. Restoring the previous version reinstates the correct content without manual reconstruction, directly satisfying the requirement to recover the latest valid version after an accidental overwrite by an older draft.

Any change affecting the scope baseline must pass through Integrated Change Control, so the project manager's first action is documenting and submitting a formal change request. Approval by the change control board follows; implementing the change beforehand bypasses governance and invalidates the baseline.

The product backlog is the single ordered list of all features, requirements and work planned for the project, from which sprint backlogs are drawn. It matches the description of features to be developed across multiple sprints.

With cost performance expected to continue, EAC equals BAC divided by the cost performance index (CPI). Here CPI is EV/AC = 120,000/130,000 ≈ 0.9231, so EAC = 200,000/0.9231 ≈ $216,667. This satisfies the stem's assumption of ongoing variance, unlike the atypical-variance formula.

Jira is built around Agile workflows, offering Scrum boards with sprints and backlogs plus Kanban boards with work-in-progress limits. This satisfies the stem's requirement for a tool specifically designed for Agile, supporting both Scrum and Kanban.

"As a [role], I want [goal], so that [benefit]" is the canonical user story template, and this option instantiates all three clauses correctly: customer, viewing order history, and the tracking benefit. It satisfies the stem's agile requirement by capturing the requirement from the user's perspective rather than as a technical specification.

In a fixed-price contract the seller agrees to deliver the defined scope for a set price, so any cost overruns from underestimated effort, resources or duration are absorbed by the seller. The buyer pays the agreed amount regardless, placing cost risk squarely on the seller.