Incorrect. The CPI is not 1.10. A CPI greater than 1.0 would indicate favorable cost performance, but the project's EV is lower than its AC.

Incorrect. 1.42 results from reversing the CPI calculation and dividing AC by EV. CPI must be calculated as EV divided by AC, not AC divided by EV.

Incorrect. Although a CPI of 0.80 would also indicate an over-budget condition, it is not the result obtained from the figures provided.

Incorrect. The project manager is accountable for overall project leadership, integration, coordination, and delivery. While the project manager supports requirements-related activities, detailed elicitation, analysis, and documentation of business requirements are primarily led by the business analyst.

Incorrect. The quality lead focuses primarily on quality planning, assurance, control, and verification that deliverables satisfy applicable quality requirements. Clarifying and documenting underlying business requirements is not the quality lead’s primary responsibility.

Incorrect. The development team uses requirements to design and build the solution and can provide technical input. However, developers would not normally take the lead in eliciting and documenting the stakeholders’ underlying business requirements.

Incorrect. The project sponsor provides strategic direction, organizational support, funding, and high-level decision-making. The sponsor may help resolve significant issues but does not normally lead detailed requirements elicitation and documentation.

Incorrect. The development team should not implement a change that can affect approved baselines before the change has been properly assessed and authorized.

Incorrect. A change request should not automatically be rejected simply because testing has started. Its impact and value should first be evaluated through the established change control process.

Incorrect. The sponsor may have an important governance role, but the project manager should not bypass the established change control process by asking the sponsor to make an informal implementation decision.

Incorrect. Frequent customer and stakeholder feedback is valuable in Agile and should not generally be discouraged. The issue is how changes are handled while protecting the purpose of the Sprint.

Incorrect. Developers are appropriately concerned about achieving the Sprint Goal. Agile flexibility does not mean accepting every change immediately without considering its effect on the Sprint Goal.

Incorrect. Nothing in the scenario indicates that Agile events themselves are consuming excessive time. The problem concerns frequent changes and their effect on Sprint focus and predictability.

Incorrect. New stakeholder requests should not automatically replace work already selected for the current Sprint. The requests should first be captured and evaluated rather than immediately disrupting the Sprint.

Incorrect. A Sprint is a fixed-length event. Extending the Sprint to accommodate additional requirements undermines the timebox and is not the appropriate response to new requests.

Incorrect. Velocity may help with forecasting, but it should not determine whether a new request enters the Product Backlog. The request should first be captured and prioritized based on value and need.

Incorrect. The Product Owner manages and orders the Product Backlog and represents product value and stakeholder needs. However, in the context presented, the broader coordination and removal of external organizational interference is expected from the project manager.

Incorrect. The Project Sponsor provides organizational support, direction, and sponsorship but would not normally manage day-to-day stakeholder interruptions affecting the development team.

Incorrect. The Development Team should remain focused on delivering the Sprint work. Requiring developers themselves to manage external stakeholder pressure would further distract them from their work.

Incorrect. Agile encourages frequent stakeholder collaboration and feedback. Restricting communication would reduce transparency and responsiveness rather than improve planning.

Incorrect. Sprint duration should not be routinely increased simply to absorb additional work. Stable Sprint lengths support consistency and predictability.

Incorrect. Customer feedback is valuable in Agile and should not be blocked by unnecessary approval processes. New feedback can be captured, evaluated, and prioritized through the Product Backlog.

Incorrect. Continuing work without first resolving the uncertainty may lead to wasted effort or work that conflicts with the eventual decision. The project manager needs objective information about the proposed change before priorities can be clarified.

Incorrect. The requirement may be mandatory, but the project manager should still assess its impact before determining how it will be incorporated. Mandatory does not mean bypassing appropriate analysis and governance.

Incorrect. Escalation may ultimately be necessary because the sponsor and regulatory stakeholder disagree, but the project manager should first perform the impact analysis so that the governance body receives objective information and viable options.

Incorrect. The Product Owner can prioritize and order backlog items, but backlog prioritization does not provide authority to approve a change to formally controlled project baselines.

Incorrect. The sponsor provides funding, strategic support, and executive direction, but in this scenario formal changes to approved project scope are governed through the established change control process.

Incorrect. A regulatory stakeholder may establish a mandatory compliance requirement, making the requirement important or unavoidable. However, this does not mean the stakeholder directly modifies the project’s approved scope baseline.

Incorrect. Arbitrarily moving developers to secondary or unrelated work does not necessarily maximize project value. The project manager should identify valuable, high-priority work that is not affected by the current blockage.

Incorrect. Preparing formal change documentation is not primarily the development team’s responsibility. The team should remain focused on delivery work that can continue while the project manager manages the stakeholder and governance issue.

Incorrect. Overtime should not be the default response to delays or stakeholder conflict. It can create an unsustainable pace and does not address the underlying impediment.

Incorrect. Focusing on value is important when evaluating whether project outcomes provide intended benefits. However, the scenario specifically emphasizes considering multiple interconnected project factors rather than focusing primarily on value.

Incorrect. Embedding quality ensures that processes and deliverables meet applicable quality expectations. The issue here is broader and involves the interaction among compliance, scope, schedule, cost, stakeholders, governance, and funding.

Incorrect. Accountable leadership is relevant to responsible decision-making and ownership. However, the defining characteristic of this scenario is the need to evaluate several interconnected elements and their combined impact on the project.

Incorrect. Team conflict during the storming stage should be addressed, but it is a normal aspect of team development and has less immediate project-wide impact than the unplanned change.

Incorrect. The missing API documentation is an impediment and should be followed up. However, it primarily affects the blocked and dependent stories, whereas the unplanned request could affect the current release and future work.

Incorrect. Reprioritization may eventually be appropriate for the blocked story, but it does not address the broader and more urgent impact created by the stakeholder’s unplanned request.

Incorrect. Eight additional sprints at an average velocity of 20 would complete only 160 of the remaining 200 story points.

Incorrect. Thirteen sprints represents approximately the total number of sprints required for the original 260-point backlog at a velocity of 20, rather than the number of additional sprints after three have already been completed.

Incorrect. Six additional sprints would complete approximately 120 story points, leaving about 80 story points unfinished.

Incorrect. The project manager can facilitate impediment removal, coordinate with external parties, and support the team. However, the project manager should not dictate how the development team performs its technical work.

Incorrect. A stakeholder can provide requirements, feedback, and business input but does not normally determine the team’s internal technical approach for completing the work.

Incorrect. The Product Owner manages and prioritizes the Product Backlog and clarifies product requirements. The Product Owner does not normally decide how the development team technically implements or resolves a story.

Incorrect. Moving the story to another iteration without first attempting to remove the impediment is a passive response and could leave the underlying dependency unresolved.

Incorrect. A workaround may be one possible solution, but the project manager should not dictate the technical approach. The team determines how the work is performed while the project manager facilitates removal of the impediment.

Incorrect. Replacing the vendor is a disproportionate response without first attempting to resolve the immediate dependency. Vendor replacement could also introduce additional cost, risk, and delay.

Incorrect. This addresses only the privacy and schedule aspects. The project manager must consider the broader combination of compliance, environmental, cost, and schedule impacts.

Incorrect. Supplier compliance is important, but immediately replacing the supplier addresses only one component of the overall situation and may itself create additional risks.

Incorrect. The project manager should not attempt to bypass or persuade the legal function to accept a noncompliant product. Mandatory compliance requirements must be appropriately addressed.

Incorrect. The legal team provides legal advice and identifies legal or regulatory concerns, but the scenario does not give it authority over the sustainability-related supplier decision.

Incorrect. The project manager should analyze the impacts, provide recommendations, and escalate the matter appropriately, but should not independently make a strategic decision that may conflict with organizational sustainability requirements.

Incorrect. The scenario explicitly limits the compliance officer's approval authority to data privacy decisions, so that authority does not extend to the supplier sustainability decision.

Incorrect. The supplier's environmental compliance is a separate issue and does not directly resolve the product's data privacy noncompliance.

Incorrect. The project manager should not immediately implement a design change before understanding its implications and obtaining input from the person with the appropriate compliance authority.

Incorrect. A make-or-buy analysis evaluates whether work should be performed internally or externally. That is not the primary analysis required for this privacy compliance issue.

Incorrect. The compliance officer's authority in the scenario is specifically related to privacy decisions. The project manager should not transfer responsibility for leadership's broader risk decision to the compliance officer.

Incorrect. The scenario states that leadership has decided to maintain the planned launch. Changing the schedule is therefore not the appropriate immediate action.

Incorrect. Focusing all remaining resources on the supplier issue addresses only one aspect of the overall risk situation and is not justified by the leadership decision.

Incorrect. The project manager provides overall oversight, coordination, and integration of project activities but is not directly responsible for performing the subcontractor's contracted work.

Incorrect. The procurement manager supports procurement and supplier-management activities but does not perform the wall-sheeting work.

Incorrect. The project sponsor provides executive support and governance but is not responsible for executing subcontracted construction activities.

Incorrect. Supplier preferences may be relevant when evaluating response options, but the project manager should first understand the impact of the delay on the overall project.

Incorrect. Parallel activities may help mitigate the schedule impact, but they are potential responses. The schedule impact must first be assessed.

Incorrect. The subcontractor's missed commitment is an issue that may require contractual or procurement action, but the project manager's immediate project-level concern is its impact on the schedule.

Incorrect. Delivery timing is an important consideration, particularly because the affected activity is on the critical path, but schedule alone is insufficient for supplier selection.

Incorrect. A make-or-buy analysis determines whether work or products should be produced internally or obtained externally. The issue here is evaluating an alternative external supplier.

Incorrect. Selecting solely on earliest delivery could introduce quality or technical problems. The alternative must satisfy the project's requirements before it is accepted.

Incorrect. Overlapping activities can be a form of fast tracking, but doing so automatically without analyzing dependencies and risks could create rework or additional problems.

Incorrect. Replacing the subcontractor is one possible procurement response, but it should not be selected before analyzing the schedule and available recovery options.

Incorrect. Extending the schedule immediately accepts the delay without first evaluating whether the lost time can be recovered through appropriate schedule adjustments.

Incorrect. The project manager provides overall oversight, coordination, and management of project activities but is not the party performing the subcontracted wall-sheeting work.

Incorrect. The procurement manager supports procurement and supplier management activities but is not directly responsible for performing the subcontractor contracted work.

Incorrect. The project sponsor provides executive support and governance but does not have operational responsibility for the subcontractor work.