PMP · Question #106
A project manager assigned team members to work in pairs on a large amount of technical reports. At times, the project manager noticed that important information was not shared properly among the team
The correct answer is A. Incorrect communication techniques applied during implementation. The fundamental issue causing delivery delays and project failure, despite pairing, is the improper sharing of information, indicating a breakdown in communication practices.
Question
Options
- AIncorrect communication techniques applied during implementation
- BLack of team member training on documentation planning
- CImproper assignment of tasks to team member pairings
- DTeam cohesiveness was lost because team members worked in pairs
How the community answered
(37 responses)- A84% (31)
- B11% (4)
- C3% (1)
- D3% (1)
Why each option
The fundamental issue causing delivery delays and project failure, despite pairing, is the improper sharing of information, indicating a breakdown in communication practices.
The core problem described is that 'important information was not shared properly among the team,' which directly points to a failure in the communication methods or techniques used during the project's execution phase, leading to delays and project failure.
While documentation planning is important, the problem explicitly states information was not *shared properly*, implying an issue with communication *during implementation*, not just the initial planning of documentation.
The problem statement does not imply that pairing itself was improper, but rather that despite pairing, information sharing failed, suggesting a communication breakdown rather than an assignment issue.
Working in pairs is often used to *enhance* cohesiveness and knowledge sharing; it is unlikely to be the root cause of lost cohesiveness or information sharing failure without other contributing factors.
Concept tested: Communication management in project execution
Topics
Community Discussion
4
Samuel O.Jul 5, 2026A is correct. The root cause here is that information sharing broke down across the pairs, which points to incorrect communication techniques being applied during implementation rather than a problem with the pairing concept itself. In my experience managing technical teams, when you split work into silos you have to build in structured cross-communication from day one or exactly this kind of information gap happens.
Dervla O.Jul 5, 2026I first leaned toward C because pairing the wrong people together sounds like a plausible reason for information gaps. But re-reading the stem, the real issue is that important information was not shared properly among the team, which points directly to a communication breakdown during execution rather than a task assignment problem. A captures this because the root cause is how information flowed, or failed to flow, once the work started. The pairing setup is just the context, not the underlying cause of the delays and failure.
Grace U.Jul 5, 2026I first leaned toward C, thinking the pairings themselves were the problem, but the real issue is that information was not shared properly among the team, which points directly to a communication breakdown rather than task assignment. The stem is describing a failure in how information flows between people, which makes A the root cause.
Zlatan X.Jul 5, 2026Confirmed A. Poor communication techniques broke information flow and killed benefits realization.