PMP · Question #1297
A project manager is part of a distributed team. The project team is using a product backlog, but due to an excessive workload, the backlog items are not very detailed. In the retrospective, a couple
The correct answer is D. Ask the team to outline their expectations and confirm with them the approach to use for. This approach ensures that the team members' concerns are directly addressed and that the chosen method for knowledge transfer aligns with their expectations. It fosters a collaborative environment where team members feel heard and involved in the decision-making process, which c
Question
A project manager is part of a distributed team. The project team is using a product backlog, but due to an excessive workload, the backlog items are not very detailed. In the retrospective, a couple of new team members are raising the issue of knowledge transfer inside the team. What should the project manager do?
Options
- AOrganize knowledge-sharing workshops and ask one of the senior team members to facilitate
- BHire a technical writer to document the work completed to date and develop a handover
- CEnsure that formal email communication is used when more information is needed to understand
- DAsk the team to outline their expectations and confirm with them the approach to use for
How the community answered
(45 responses)- A11% (5)
- B7% (3)
- C2% (1)
- D80% (36)
Explanation
This approach ensures that the team members' concerns are directly addressed and that the chosen method for knowledge transfer aligns with their expectations. It fosters a collaborative environment where team members feel heard and involved in the decision-making process, which can lead to more effective and tailored knowledge-sharing practices.
Topics
Community Discussion
5D is the right call here. The exam tests servant leadership in agile environments, which means the PM facilitates team self-organization rather than imposing a top-down fix. New team members raised the knowledge transfer issue in the retrospective, so the PM should ask the team to outline their expectations and collaboratively confirm the approach to use. This directly addresses the backlog detail problem and the knowledge gap while empowering the team to own the solution.
I first leaned toward A because a workshop sounds proactive, but that is the PM deciding the solution instead of letting the team weigh in. Think of it like a barn raising where you show up with a blueprint nobody agreed on, versus calling a quick huddle so everyone can say what they actually need before the nails fly. In agile, when new folks flag a knowledge gap and the backlog is thin, the move is to facilitate the team's own conversation about expectations and approach, which is exactly what D does. Handing it to one senior member or a hired writer skips that collaboration step the retrospective is
Nice analogy, and D is the right call, but I'd add that the key phrase in the stem is "expectations and approach" which maps directly to facilitation rather than knowledge transfer, so the distractor about bringing in a senior member is the trap for people who confuse mentoring with self-organization.
Our group landed on D because the retrospective is exactly where the team should self-organize and co-create solutions, not have the PM hand down fixes. A is tempting since workshops sound proactive, but the PM picking who facilitates skips the team-driven approach that agile calls for. B and C are worse since they push toward documentation-heavy, formal communication that does not fit the collaborative spirit of a distributed agile team. Saw this one on my exam last month and almost clicked A because the knowledge transfer angle made me think training session right away. Re-read the stem and caught that it was raised in the
Good catch on A being the trap, and the reason it fails is that a PM assigning a facilitator is like a restaurant manager telling the kitchen staff who should lead the post-dinner-rush debrief instead of letting the cooks who actually burned the pancakes sort it out themselves, which is exactly the self-organizing principle the retrospective is built on.