In the PMBOKGuide, particularly within the Manage Project Knowledge process, a clear distinction is made between two types of knowledge: Explicit and Tacit.
* Tacit Knowledge (Choice C): This is personal knowledge that is difficult to express or formalize. It includes Expert Judgment, insights, experience, " know-how, " and beliefs. It is often shared through interpersonal interaction, mentoring, and social connection. Because it is embedded in the individual ' s mind and influenced by their unique context, it cannot be easily written down or stored in a database.
* Explicit Knowledge (Choice A, B, and D): This is knowledge that can be codified using symbols such as words, numbers, and pictures. It can be easily documented and shared.
* Risk Register (Choice A): A formal document containing identified risks and their characteristics.
* Project Requirements (Choice B): Documented needs or conditions that must be met.
* Make-or-buy Analysis (Choice D): A documented technique and result used to determine whether work should be performed internally or purchased from outside sources.
The goal of the Manage Project Knowledge process is to use existing organizational knowledge and create new knowledge to achieve the project ' s objectives. While explicit knowledge is managed via Information Management, tacit knowledge is managed through Knowledge Management (e.g., networking and communities of practice) because it resides within the experts themselves.