- A
Reduce the sprint backlog size to 50% of current capacity to allow more time for testing.
Why wrong: This does not address the root cause of defects found late; it only reduces throughput.
- B
Require that all code have unit tests before being merged, and implement continuous integration to run automated tests every few hours.
This addresses the root cause of late defect discovery by shifting quality left.
- C
Ask the product owner to defer non-critical features to later releases.
Why wrong: This does not improve the development process; it only reprioritizes work.
- D
Add two more testers to the team to increase testing capacity.
Why wrong: Adding testers does not prevent defects; it only increases capacity to test, but the bottleneck may shift.
Quick Answer
The answer is to require unit tests before merging code and implement continuous integration with automated tests running every few hours. This directly addresses the root cause of defect rework and the tester bottleneck by shifting quality left—catching errors at the unit level rather than during end-of-sprint integration testing. In Agile, deferred integration and missing unit tests force testers to find defects late, creating rework that consumes developer time and stalls velocity. On the PMP exam, this scenario tests your understanding of built-in quality and continuous integration as tools for agile velocity improvement; a common trap is choosing to add more testers or extend sprint duration, which only masks the symptom. Remember the mnemonic “Test Early, Integrate Often”—if unit tests aren’t written before merging, you’re building on a shaky foundation, and without CI, you’re waiting for disaster at the sprint’s end.
PMP Process — Managing Technical Aspects Practice Question
This PMP practice question tests your understanding of process — managing technical aspects. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
You are managing a software development project using an Agile approach. The team consists of 8 developers and 2 testers. During the last three sprints, the team has consistently delivered about 70% of planned story points. The product owner is frustrated because key features are being delayed. The team reports that they are spending too much time fixing defects found during testing, and that the testers are a bottleneck. Upon reviewing the definition of done, you notice that unit tests are required but not always written, and integration tests are done only at the end of the sprint. What is the BEST course of action to address the root cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"best"Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
Clue:
"always"Why it matters: Absolute qualifier. An answer using 'always' is only correct if there are genuinely no exceptions — absolute statements are often wrong in networking.
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
Require that all code have unit tests before being merged, and implement continuous integration to run automated tests every few hours.
Option B directly addresses the root cause: the team is spending too much time fixing defects because unit tests are not always written and integration tests are deferred to the end of the sprint. By requiring unit tests before merging and implementing continuous integration (CI) with automated tests running every few hours, defects are caught earlier, reducing rework and eliminating the tester bottleneck. This aligns with Agile principles of built-in quality and early feedback, which improves velocity and predictability.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Reduce the sprint backlog size to 50% of current capacity to allow more time for testing.
Why it's wrong here
This does not address the root cause of defects found late; it only reduces throughput.
- ✓
Require that all code have unit tests before being merged, and implement continuous integration to run automated tests every few hours.
Why this is correct
This addresses the root cause of late defect discovery by shifting quality left.
Clue confirmation
The clue words "best", "always" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Ask the product owner to defer non-critical features to later releases.
Why it's wrong here
This does not improve the development process; it only reprioritizes work.
- ✗
Add two more testers to the team to increase testing capacity.
Why it's wrong here
Adding testers does not prevent defects; it only increases capacity to test, but the bottleneck may shift.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often choose to add resources (Option D) or reduce scope (Option A/C) instead of addressing the process and technical practice gap—specifically, the lack of automated testing and continuous integration, which is the true root cause of the bottleneck and low velocity.
Detailed technical explanation
How to think about this question
Continuous integration (CI) with automated unit tests ensures that every code commit is validated immediately, preventing integration hell and reducing the feedback loop from days to minutes. In Agile, the definition of done should include passing all unit tests and integration tests; without this, technical debt accumulates, and the team's velocity becomes unreliable. Real-world scenarios show that teams adopting CI with test automation often see a 30-50% reduction in defect escape rates and improved sprint predictability.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Process — Managing Technical Aspects — study guide chapter
Learn the concepts, then practise the questions
- →
Process — Managing Technical Aspects practice questions
Targeted practice on this topic area only
- →
All PMP questions
892 questions across all exam domains
- →
Project Management Professional PMP study guide
Full concept coverage aligned to exam objectives
- →
PMP practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related PMP practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
People — Leading Projects practice questions
Practise PMP questions linked to People — Leading Projects.
Process — Managing Technical Aspects practice questions
Practise PMP questions linked to Process — Managing Technical Aspects.
Business Environment — Strategy and Value practice questions
Practise PMP questions linked to Business Environment — Strategy and Value.
Business Environment: strategy and project benefits practice questions
Practise PMP questions linked to Business Environment: strategy and project benefits.
PMP fundamentals practice questions
Practise PMP questions linked to PMP fundamentals.
PMP scenario practice questions
Practise PMP questions linked to PMP scenario.
PMP troubleshooting practice questions
Practise PMP questions linked to PMP troubleshooting.
Practice this exam
Start a free PMP practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this PMP question test?
Process — Managing Technical Aspects — This question tests Process — Managing Technical Aspects — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Require that all code have unit tests before being merged, and implement continuous integration to run automated tests every few hours. — Option B directly addresses the root cause: the team is spending too much time fixing defects because unit tests are not always written and integration tests are deferred to the end of the sprint. By requiring unit tests before merging and implementing continuous integration (CI) with automated tests running every few hours, defects are caught earlier, reducing rework and eliminating the tester bottleneck. This aligns with Agile principles of built-in quality and early feedback, which improves velocity and predictability.
What should I do if I get this PMP question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "best", "always". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
3 more ways this is tested on PMP
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Your agile project has been experiencing declining velocity over the last three sprints. During the retrospective, the team identifies that they are spending too much time on unplanned work and technical debt. The product owner wants to maintain the current scope. Which THREE actions should the project manager take? (Choose three.)
hard- A.Ask the product owner to reduce the scope of the next sprint
- ✓ B.Allocate a portion of each sprint to address technical debt
- ✓ C.Implement a policy to shield the team from external interruptions during sprints
- D.Add more developers to the team to increase capacity
- ✓ E.Work with the product owner to improve the 'definition of ready' for user stories
Why B: Options A, C, and E are correct. A: Allocating time to reduce technical debt helps improve velocity. C: Refining the definition of ready reduces unplanned work. E: Shielding the team protects them from interruptions. Option B conflicts with PO's wish; option D is reactive and may not address root cause.
Variation 2. In an agile project, the team's velocity has been declining over the last three sprints. The team is delivering fewer story points each sprint. The product owner is concerned about the release date. What should the Scrum Master do first?
medium- A.Ask the product owner to descope some features to meet the release date
- ✓ B.Facilitate a retrospective focused on identifying root causes of the declining velocity
- C.Add more story points to the next sprint to compensate for the loss
- D.Extend the sprint duration to give the team more time
Why B: Option D is correct: Understanding the root cause is the first step. Option A ignores the causes, B is reactive, C may be a result but not the first action.
Variation 3. In your agile project, the team's velocity has been declining over the past three sprints from 30 to 25 to 20 story points. The team members report feeling overworked and demotivated. The daily standup meetings are running long, and the product owner is adding too many stories each sprint. What should the project manager do FIRST?
medium- A.Ask the product owner to reduce the number of stories per sprint
- ✓ B.Facilitate a retrospective to identify root causes and collaboratively develop improvement actions
- C.Reduce the sprint length to create urgency and improve focus
- D.Mandate that the team must increase velocity to 30 story points next sprint
Why B: Option D is correct because the project manager should facilitate a retrospective to identify root causes and let the team propose solutions. Option A is a temporary fix. Option B addresses symptoms but not root causes. Option C is dictatorial and not agile.
Last reviewed: Jun 11, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.