PMP · Question #287
A project is in the knowledge transfer phase, and a few subject matter experts (SMEs) went to the client site for knowledge transfer. The SMEs captured various process deviations without sharing with
The correct answer is D. Ask the SMEs to share the knowledge transfer documents with all other members by placing the. To ensure knowledge transfer across the entire team, the project manager should instruct the SMEs to centralize and share all knowledge transfer documents and captured deviations with other team members.
Question
A project is in the knowledge transfer phase, and a few subject matter experts (SMEs) went to the client site for knowledge transfer. The SMEs captured various process deviations without sharing with the project team. How can the project manager ensure knowledge transfer across the team?
Options
- AAsk the project team to run a deviation log review meeting with the client, highlighting that the
- BAsk the project team to facilitate a lessons learned session during the project closure phase to
- CAsk the project management office (PMO) to provide team members with real-time visibility for
- DAsk the SMEs to share the knowledge transfer documents with all other members by placing the
How the community answered
(52 responses)- A15% (8)
- B10% (5)
- C4% (2)
- D71% (37)
Why each option
To ensure knowledge transfer across the entire team, the project manager should instruct the SMEs to centralize and share all knowledge transfer documents and captured deviations with other team members.
Running a deviation log review meeting with the client specifically for the project team, while potentially informative, primarily focuses on client interaction rather than the internal sharing of critical knowledge and captured deviations amongst the wider project team members.
Waiting until project closure for a lessons learned session is too late to ensure effective knowledge transfer during the active knowledge transfer phase, as the immediate insights from the SMEs are needed by the team for ongoing project work.
Asking the PMO to provide real-time visibility might be a procedural step, but it doesn't directly address the specific failure of the SMEs to share their collected knowledge and deviations with the core project team members themselves.
The most direct and effective action to ensure knowledge transfer is to have the SMEs, who possess the knowledge, actively share their documents and findings by making them accessible to the entire team in a centralized location, facilitating immediate and ongoing learning.
Concept tested: Knowledge management and transfer within projects
Source: https://learn.microsoft.com/en-us/azure/devops/boards/get-started/share-information?view=azure-devops
Topics
Community Discussion
4D is correct. The SMEs are the component holding the captured knowledge, and until that artifact lands in a shared repository the rest of the team cannot realize the benefit of that transfer. Governance fails when critical information sits with individuals instead of flowing across the interdependent team.
Leaned toward B but waiting for closure is too slow, D shares knowledge now.
D is the move, but frame it as the program manager enabling knowledge transfer across components so lessons learned feed benefits realization rather than staying siloed in a single project closure.
I first leaned toward B because lessons learned sounds like the safe PMI default for capturing deviations. The problem is B defers the knowledge transfer to project closure, which does nothing about SMEs sitting on undocumented process deviations right now while the transfer is actively happening. D is the immediate fix: get those documents into a shared repository so the rest of the team has access without waiting. PMI loves the centralized knowledge management angle, and D maps directly to that principle. Card this one with a tag for Manage Project Knowledge. The key trigger phrase is SMEs captured without sharing. That signals a distribution problem