PMBOK® GUIDE SIXTH EDITION

Potential information in organizational knowledge repositories

Tacit knowledge is personal and difficult to express, and is generally not found in organizational knowledge repositories. One of the important purposes of knowledge management is to transform tacit knowledge into explicit knowledge, which can then be stored in repositories.

The organizational knowledge repositories for storing and retrieving information include, but are not limited to:

• Configuration management knowledge repositories containing the versions of software and hardware components and baselines of all performing organization standards, policies, procedures, and any project documents;
• Financial data repositories containing information such as labor hours, incurred costs, budgets, and any project cost overruns;
• Historical information and lessons learned knowledge repositories (e.g., project records and documents, all project closure information and documentation, information regarding both the results of previous project selection decisions and previous project performance information, and information from risk management activities);
• Issue and defect management data repositories containing issue and defect status, control information, issue and defect resolution, and action item results;
• Data repositories for metrics used to collect and make available measurement data on processes and products; and Project files from previous projects (e.g., scope, cost, schedule, and performance measurement baselines, project calendars, project schedule network diagrams, risk registers, risk reports, and stakeholder registers).