PMP Process — Managing Technical Aspects Practice Question
Your project's sponsor requests that you skip user acceptance testing (UAT) to recover schedule delays. The team has already performed thorough internal testing. What should you do FIRST?
⚠ Common exam trap
It's easy for candidates to think internal testing is sufficient to replace UAT, but PMP emphasizes that UAT validates the product from the user's perspective, which is a distinct and mandatory quality gate that cannot be substituted by technical testing alone.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Explain the risks of skipping UAT and propose a compressed UAT schedule
Skipping UAT violates the project's quality management plan and risks delivering a product that does not meet user needs, even if internal testing passed. The first step is to communicate the risks of skipping UAT to the sponsor and propose a compressed schedule as a compromise, which aligns with the PMI's emphasis on stakeholder communication and risk management. This approach balances schedule recovery with maintaining quality assurance through user validation.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Explain the risks of skipping UAT and propose a compressed UAT schedule
Why this is correct
The project manager's primary responsibility is to balance project constraints while ensuring quality and managing risks effectively. By explaining the potential negative consequences of omitting User Acceptance Testing, such as increased post-implementation defects and user dissatisfaction, the PM educates the sponsor on critical project risks. Proposing a compressed UAT schedule demonstrates a proactive approach to mitigating risks while accommodating schedule pressures, aligning with effective stakeholder communication and problem-solving.
- ✗
Skip UAT and add a warranty period to address any issues after release
Why it's wrong here
Skipping User Acceptance Testing and instead relying on a warranty period is a reactive approach that fails to prevent defects proactively. This strategy often leads to higher costs associated with defect resolution post-release, reputational damage, and user frustration, which far outweigh the perceived time savings. A warranty addresses issues after they occur, whereas UAT aims to identify and rectify them before deployment, making it an inadequate substitute for thorough quality assurance.
- ✗
Proceed with UAT as planned without informing the sponsor
Why it's wrong here
Proceeding with UAT as planned without informing the sponsor demonstrates a critical failure in stakeholder communication and management. Ignoring a direct request from the project sponsor undermines trust and can lead to significant project governance issues, potentially jeopardizing future support or even project cancellation. Effective project management requires transparent communication and collaborative problem-solving, not unilateral decision-making that disregards key stakeholder input.
- ✗
Agree to skip UAT to accommodate the sponsor's request
Why it's wrong here
Agreeing to skip User Acceptance Testing solely to accommodate a sponsor's request compromises the project's quality baseline and violates professional ethics. This decision introduces substantial risks, including delivering a product that does not meet user needs or contains critical defects, leading to rework, increased costs, and reputational damage. A project manager has a professional obligation to protect project quality and advocate for processes that ensure successful delivery, even when facing pressure.
Go deeper
Related to this question
Learn chapter
Introduction to the PMP Exam and Project Management Basics
Key term
Project Management Plan
A formal, approved document that defines how a project is executed, monitored, controlled, and closed, serving as the single source of truth for the project team.
Key term
Quality Management
Quality Management is the practice of defining, monitoring, and controlling the processes and deliverables of a project to ensure they meet the required standards and stakeholder expectations.
About these practice questions
One of 800 original PMP practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PMP practice question is part of Courseiva's free PMI certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PMP exam.