Project Knowledge Standard: Manage Project Knowledge Process
PMBOK v8 Definition
The PMBOK v8 defines project management as "the application of knowledge, skills, tools, and techniques to project activities in order to meet or exceed stakeholder needs and expectations from a project." The Manage Project Knowledge process is the process of using existing knowledge and creating new knowledge to achieve the project's objectives and contribute to organizational learning. This process belongs to the Executing Process Group and the Project Communications Management Knowledge Area.
Why It Matters for the Exam
This concept appears frequently in PMI exam questions that test your understanding of how knowledge is captured, shared, and applied across the project lifecycle. It is commonly tested in situational questions where a project team repeats mistakes or fails to leverage lessons learned from previous projects. The exam emphasizes the distinction between explicit knowledge (documented) and tacit knowledge (personal experience), and how both must be managed systematically.
Key Points to Remember (for the exam)
- Main Input: Lessons learned register, project management plan, enterprise environmental factors, organizational process assets, deliverables
- Main Output: Lessons learned register updates, project management plan updates (any component), organizational process asset updates
- Key Tool: Knowledge management (includes after-action reviews, in-progress postmortems, storytelling, retrospective meetings)
- Key Tool: Information management (formal documentation and distribution)
- Key Interpersonal Skill: Active listening, facilitation, leadership, networking, political awareness
- Common Confusion: Confusing "Manage Project Knowledge" with "Monitor and Control Project Work" — Knowledge focuses on creating and sharing knowledge, not just tracking work
- Critical Distinction: Tacit knowledge (personal, hard to formalize) vs. explicit knowledge (documented, easy to transfer) — Both must be managed, but with different techniques
Typical PMI Exam Example
A project manager notices that the engineering team repeatedly makes the same design errors that were identified and documented in a previous project. The project manager decides to hold a retrospective meeting where team members share their experiences and discuss improvements. Which process is being performed? → Manage Project Knowledge (using knowledge management tools like retrospective meetings to transfer tacit knowledge).
PMI Exam Traps
- Trap: Thinking "Manage Project Knowledge" is only about documentation
- Reality: It equally emphasizes tacit knowledge transfer through interpersonal techniques like storytelling and after-action reviews
- Trap: Confusing "lessons learned register" as a final project document only
- Reality: The lessons learned register is a living document updated continuously throughout the project, not just at the end
- Trap: Assuming knowledge management is a "Planning" process
- Reality: Manage Project Knowledge is an Executing process — knowledge is actively managed during project execution, not just planned
- Trap: Believing knowledge management only applies to successful projects
- Reality: Lessons learned from failures and mistakes are equally valuable for organizational learning
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Lessons Learned Register | Output of Manage Project Knowledge | This register is updated continuously and feeds into organizational process assets |
| Organizational Process Assets | Input to Manage Project Knowledge | Historical knowledge from past projects is a key input; updates become new assets |
| Project Management Plan | Input to Manage Project Knowledge | Any component can be updated based on new knowledge gained |
| Manage Communications | Complementary Process | Knowledge is shared through communication channels; Manage Knowledge focuses on content, Manage Communications focuses on distribution |
Quick Review Questions
- A project team has completed a sprint and wants to capture what worked well and what did not. Which tool or technique should the project manager use?
- What is the key difference between "knowledge management" and "information management" in the Manage Project Knowledge process?
- During project execution, a senior engineer leaves the project. The project manager realizes the engineer's expertise was never documented. Which type of knowledge was lost, and what technique could have prevented this?
- A project manager updates the lessons learned register after each milestone. During which process group does this update occur?
- Which interpersonal and team skills are specifically listed as tools for the Manage Project Knowledge process?
PMBOK v8 Reference
Section 2.8 - Manage Project Knowledge (Figure 2-8: Manage Project Knowledge Inputs, Tools and Techniques, and Outputs)