PMP Process — Managing Technical Aspects Practice Question
During a daily standup, a developer mentions that a critical integration task will take longer than expected because of a technical dependency on another team. The project is on a tight schedule. Which THREE actions should you take?
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
✓
Help the team remove the impediment by coordinating with the other team's manager
Removing impediments is a key responsibility of the project manager or Scrum Master; coordinating with the other team's manager addresses the dependency promptly. Option C is correct because the product owner should reprioritize the backlog if the delay impacts the sprint goal, ensuring the team works on the most valuable items. Option E is correct because updating the risk register with the potential delay and mitigation actions is a standard risk management practice to track and communicate risks. Option B is incorrect because adding tasks does not resolve the delay and may overwhelm the team. Option D is incorrect because informing the sponsor of a delay is premature; the team should first assess the impact and explore mitigation options.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Help the team remove the impediment by coordinating with the other team's manager
Why this is correct
As a Scrum Master, facilitating impediment removal is a primary responsibility to maintain team flow and productivity. When an impediment involves an external dependency, such as another team, the Scrum Master should proactively coordinate with the relevant manager or stakeholder to resolve the issue. This action directly supports the development team and protects the sprint goal from external blockers, demonstrating servant leadership.
- ✗
Add more tasks to the sprint to keep the team busy
Why it's wrong here
Adding more tasks to a sprint, especially when a critical impediment already exists, is counterproductive and violates the principle of a stable sprint commitment. This action would further overload the team, dilute their focus from resolving the current issue, and increase the risk of failing to meet the sprint goal or delivering low-quality work. The team's capacity should be respected, and their focus should be on resolving the impediment.
- ✓
Ask the product owner to reprioritize the backlog if the delay affects the sprint goal
Why this is correct
If a critical impediment threatens the sprint goal, the Scrum Master should facilitate a conversation with the Product Owner to assess the impact and consider backlog adjustments. The Product Owner, responsible for maximizing value, may need to reprioritize remaining sprint backlog items or even negotiate the sprint goal with the team. This ensures that even with a delay, the most valuable work is still pursued within the current sprint.
- ✗
Immediately inform the sponsor that the project will be delayed
Why it's wrong here
Immediately escalating a potential delay to the sponsor without first attempting to resolve the impediment within the team or with direct stakeholders is premature. This action undermines the team's ability to self-organize and problem-solve, and it can create unnecessary alarm among senior stakeholders. Effective project management emphasizes resolving issues at the lowest possible level before broader escalation.
- ✓
Update the risk register with the potential delay and mitigation actions
Why this is correct
A potential delay due to a critical impediment represents a project risk that must be formally documented. Updating the risk register ensures that the potential impact, probability, and planned mitigation strategies are recorded and tracked for transparency. This proactive risk management approach allows for continuous monitoring and provides clarity to stakeholders regarding potential challenges and the steps being taken to address them.
Visual reference
Go deeper
Related to this question
Learn chapter
Introduction to the PMP Exam and Project Management Basics
Key term
Scrum Methodology
Scrum is a lightweight process framework that helps teams deliver complex projects in small, iterative chunks called sprints.
Key term
Sprint Planning
Sprint Planning is a time-boxed meeting at the start of a Scrum sprint where the team decides what work they can deliver and how they will do it.
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.