---
ref_id: PR29
ref_type: Process
ref_name: "Manage Project Knowledge"
version: "1.0.0"
status: Active
pmbok8_source: "PMBOK8 Guide §2.8"
companion_ref_shortcode: PG-APG-6.2
related_skills:
  - SKL-04-03
related_artifacts:
  - A30
file_path: "reference/processes/PR29-manage-project-knowledge.md"
---
# PR29 — Manage Project Knowledge

## Classification
- **Performance Domain:** Team / Delivery
- **Process Group:** Executing
- **PMBOK 8 Reference:** Section 2.8 (Team Performance Domain)
- **Process Groups Practice Guide Reference:** Section 6.2

---

## Purpose
Manage Project Knowledge is the process of using existing knowledge and creating new knowledge to achieve the project’s objectives and contribute to organizational learning. The key benefits are: prior organizational knowledge is leveraged to improve project outcomes, and knowledge created by the project is available to support organizational operations and future projects.

---

## Inputs
- Project management plan (all components)
- Project documents: lessons learned register, project team assignments, resource breakdown structure, stakeholder register
- Deliverables
- Enterprise environmental factors
- Organizational process assets

---

## Tools & Techniques
- Expert judgment
- Knowledge management (communities of practice, workshops, knowledge fairs, shadowing)
- Information management (PMIS, databases, document libraries)
- Interpersonal and team skills (active listening, facilitation, leadership, networking, political awareness)

---

## Outputs
- Lessons learned register
- Project management plan updates (any component)
- Organizational process assets updates

---

## Key Concepts
- Explicit knowledge: codified using words, pictures, and numbers; easily shared but lacks context.
- Tacit knowledge: personal insights, experience, beliefs; difficult to codify but rich in context; shared best through conversations and interactions.
- Creating an atmosphere of trust is the most important prerequisite for effective knowledge sharing.
- Knowledge management is not just documenting lessons learned at project end — it is an ongoing process throughout the project.

---

## Source Traceability
- PMBOK 8: Section 2.8 (Team Performance Domain)
- Process Groups Practice Guide: Section 6.2

---

## Cross-References

| Related Item | Type | Relationship |
|---|---|---|
| A30 | Artifact | Primary artifact produced or updated by this process |
| SKL-04-03 | Skill | Skill that executes this process |

## Practitioner Notes

Practitioners executing this process should seek answers to the following questions:
1. Are both explicit and tacit knowledge capture mechanisms in place?
2. Are lessons learned documented during execution, not just at closure?
3. Is knowledge shared across the team and with the PMO knowledge base?
4. Are knowledge management roles and responsibilities defined?
5. Is the lessons learned register integrated with risk and issue logs?

## Change Log

| Version | Date | Description | Author |
|---|---|---|---|
| 1.0.1 | 2026-06-03 | Added Cross-References, Practitioner Notes, and Change Log sections (F-12 Batch 4) | PMO Director |
