Organizational Process Assets

Organizational process assets are tools (usually document or database) that can be used as template, guidance or reference toward current project. These documents are like policies, standard or procedures or maybe best practice of the company in order to run a project. An organization might keep a good interest and more likely to run similar projects with the last successful (proven track record) project; that's why it is a good idea to reuse the document template in order to start the next project.

Despite of storing only referenced files from last projects, an organization process assets also include the current running project's documents such as Project Charter and scope statement. That is why the collection of organizational process assets is usually called Knowledge Base of the project. All of predecessor process group's output will be stored in the knowledge base, e.g.: after finishing Initiating Process Group producing Project Charter, it must be stored into knowledge base. Since there is a rapid need to access the knowledge base, it must be stored in a media flexible enough to keep project's documents and to make such documents retrievable/accessible for update or just merely for reference.

=====

Trivia

=====

Now that both the enterprise environment factors and the organizational process assets have been explained, what's the difference between those two?

Answer: 

Enterprise environment factors are about the way an organization perform its business; the overall condition to which the business operated while organizational process assets are about the way an organization run its project. 

"Management is doing things right; leadership is doing the right things." -- Peter F. Drucker