PMP · Question #50
A team member in an agile project informs the project manager they might not be able to finish an assigned task on time, which could generate an obstacle for the rest of the team. What should the proj
The correct answer is A. Ask the team member to bring up the concern in the next daily meeting. An agile team member reports a potential delay that could impact other team members and the current sprint.
Question
A team member in an agile project informs the project manager they might not be able to finish an assigned task on time, which could generate an obstacle for the rest of the team. What should the project manager do?
Options
- AAsk the team member to bring up the concern in the next daily meeting
- BSend an email explaining the issue to all team members
- CReassign the task to another team member
- DMove the task to the next sprint
How the community answered
(40 responses)- A73% (29)
- B5% (2)
- C8% (3)
- D15% (6)
Why each option
An agile team member reports a potential delay that could impact other team members and the current sprint.
In agile projects, the daily stand-up (or daily scrum) is the designated forum for the team to synchronize, highlight progress, discuss impediments, and collectively address potential blockers. By bringing up the concern in this meeting, the self-organizing team can brainstorm solutions, offer support, or adjust the sprint plan together.
Sending an email is a less interactive and less immediate method for resolving impediments in an agile environment compared to the collaborative nature of a daily meeting.
Reassigning the task unilaterally without team discussion undermines the principles of self-organizing teams in agile and may not be the most efficient solution.
Moving the task to the next sprint is a significant decision that impacts sprint goals and stakeholder expectations; it should be a collective team decision made after discussing the impediment in the daily meeting, not a unilateral immediate action.
Concept tested: Agile daily stand-up and impediment resolution
Source: https://www.scrum.org/resources/what-is-scrum
Topics
Community Discussion
5A is correct. The daily standup is exactly where blockers and impediments get surfaced so the team can swarm on them, and I almost picked C the first time around because it felt proactive. Resist the urge to fix it yourself in the background, let the team own it.
Agreed on A, but the trap isn't just C, it's that people conflate surfacing the blocker at standup with actually resolving it there, which turns a 15-minute sync into a troubleshooting session.
A is correct, though I wish the option said "raise it at the next standup" rather than "bring up the concern," since the real goal is surfacing the blocker so the team can swarm or adjust. C is tempting because it feels proactive, but reassigning work unilaterally sidesteps the team's ownership and ignores whatever dependency or context caused the delay in the first place. In agile, the daily meeting is exactly the mechanism for this kind of visibility, so the team can decide together how to handle it.
Confirmed A on my last attempt. The daily scrum is exactly where impediments get surfaced so the team can self-organize around them, which is the whole point of agile. C is the trap a lot of people fall for because reassigning sounds proactive, but the PM should not be unilaterally moving work around in an agile environment. The slight quibble is that the team member could also just raise it immediately instead of waiting for the next standup, but A is the closest to how the exam wants you to handle blocker visibility.
Agreed on A, and the reason C is so tempting is that it maps to the traditional PM mindset the exam is trying to test whether you can let go of.