Do project management usually hear a little bit long word: "organizational process assets." So what is "organizational process assets" mean?
After checking the books, we learned the following meanings:
In developing project documents Project Charter and beyond, as well as any kind of all assets used to influence the success of the project can be used as organizational process assets. Any and all organizations involved in the project may have formal or informal policies, procedures, programs and principles, all of these effects must be considered. Organizational process assets also reflects the organization learned from previous projects and lessons learned knowledge, such as meeting schedules, risk data and realize the value of data. Organization organizational process assets due to the type of industry, organizations and applications varies.
For example, the organizational process assets can be grouped into the following categories.
(1) the organization of work processes and procedures.
- Organizational standard processes, such as standards, guidelines (safety and health policy, project management policy); standard software life cycle and project life cycle, as well as the quality policy and procedures (process audit, the goal to improve, checklists, as well as for internal organizational use of process definition ).
- Standard guidelines, work instructions, and implementation of recommendations of the evaluation criteria Evaluation criteria.
- Templates (such as risk templates, work breakdown structure templates and project schedule network diagram templates).
- We need to modify the guiding principles and norms of the organization's standard procedure according to the specific project.
- Organizational communication requirements (such as a specific communication technology available, allowing the use of the communication medium, record-keeping and security requirements).
- Project closure guidelines or requirements (eg, final project audits, project evaluations, product validation, and acceptance criteria).
- Financial control procedures (such as progress reports, necessary expenses and payment review, accounting codes, and standard contract provisions).
- Identify problems and defect control, defect identification and resolution of problems, issues and action tracking and defect management procedures.
- Change control procedures, including amending the formal standards, policies, plans and programs, or any project documents, as well as steps to ratify and confirm any changes should follow.
- Risk control procedures, including determining the type of risk and consequences, probability, and the probability and consequences of a matrix.
- Approval and issuance of the authorization procedures.
(2) information storage and retrieval Knowledge organization as a whole.
- Process measurement database used to collect and provide product and process measured data.
- Project files (such as scope, cost, schedule, and quality criteria, benchmarks to measure the effect of the implementation, project calendars, project schedule network diagrams, risk registers, planned response actions, and risk the consequences determined).
- Historical information and lessons learned knowledge base (such as project records and documents, all project closure information and documentation, results of previous project selection decisions and performance information; and information risk management efforts).
- Problems and defect management database, including issues related to the defect status, control information, solve problems and defects and the results of actions.
- Configuration management knowledge base, including various versions of all official reference standards, guidelines, procedures, and any project documents.
- Financial databases, including such as working hours, costs incurred, budget and any project cost overruns and other information.