PMP · Question #958
Three testers joined the project team just before the end of the build. During the project team meeting, the testers indicated that the project quality is poor, and they should not continue testing…
The correct answer is B. Ask the testers to provide additional information. C. Brainstorm the issue with the project team. D. Continue with testing according to the plan. When new testers report poor quality, the project manager should seek specific information from them, involve the team in brainstorming solutions, and continue testing as planned to gather objective data.
Question
Options
- AStop the project and review the output.
- BAsk the testers to provide additional information.
- CBrainstorm the issue with the project team.
- DContinue with testing according to the plan.
- EAsk the sponsor for assistance and guidance.
How the community answered
(24 responses)- A21% (5)
- B67% (16)
- E13% (3)
Why each option
When new testers report poor quality, the project manager should seek specific information from them, involve the team in brainstorming solutions, and continue testing as planned to gather objective data.
Stopping the project prematurely based on initial feedback, especially from new team members, is an overreaction and could cause significant and unnecessary delays.
The project manager needs specific, actionable feedback beyond a general statement of 'poor quality.' Asking for additional information, examples, and data from the testers helps quantify the problem.
Involving the entire project team in brainstorming allows for a collaborative effort to understand the root causes of the quality issues and develop effective solutions, leveraging diverse expertise.
Continuing with testing according to the plan ensures that all defects are systematically identified and logged, providing objective data for decision-making and preventing further delays by halting progress completely.
Escalating to the sponsor is a later step, only after the project team has thoroughly investigated the issue, understood its impact, and explored potential internal solutions.
Concept tested: Quality Management and Team Problem-Solving
Topics
Community Discussion
5
Luis F.Jul 5, 2026Confirmed B, C, and D on my practice exam last week. The PM mindset here is to keep things moving while you investigate, so you ask the testers for specifics (B) and brainstorm the problem with the whole team (C) instead of just halting all work. You also continue testing per the plan (D) because finding defects is literally what testing is for, and you never just stop the project because quality is poor. Option A is too extreme for a situation like this, and E is a total trap since you should never escalate to the sponsor before trying to solve it with your
Yuki V.Jul 5, 2026Just passed CAPM last month and B, C, D is the right combo here because you never stop testing over complaints without details, and stopping the project or escalating to the sponsor is premature. The testers joining late and immediately crying foul is tricky though, so does anyone know if the exam always treats continuing per plan as correct even when quality concerns seem legitimate?
Yusuf A.Jul 5, 2026My senior PM always says new people panicking about quality is normal, so B gets them talking, C brings the team together on it, and D keeps you moving since you test to find defects, not after they are all fixed. One thing I am still fuzzy on, why is A wrong here, since stopping to review output sounds like a responsible pause?
Carlos M.Jul 5, 2026Got B, C, D on my practice exam last week and the logic checks out. B makes sense because three testers showing up at the end and declaring quality poor without specifics is useless, you need the actual defect data. C follows naturally since brainstorming with the full team gets everyone aligned on what the real quality issues are instead of just the testers complaining. D is correct because you never halt testing entirely while defects get fixed, you test what you can and log everything so the plan stays on track. A and E are overreactions that would just stall the project without solving anything.
Wesley A.Jun 29, 2026Failed my first PMP attempt partly because of questions like this one. The trap here is A, because stopping the project sounds responsible when testers are raising alarms, but you do not halt everything just because new team members are unhappy. The right move is to keep testing per the plan (D) while you gather specifics from the testers (B) and work it as a team problem-solving exercise (C). E is a classic wrong answer because escalating to the sponsor before you have even investigated is a failure of your role as PM. One thing I am still sorting out, does anyone know if PMI