Page 54 -
P. 54

2 - ORGANIZATIONAL INFLUENCES AND PROJECT LIFE CYCLE






                                      ○  Organizational communication requirements (e.g., specific communication technology available,
                                      authorized communication media, record retention policies, and security requirements);
                                      ○  Procedures for prioritizing, approving, and issuing work authorizations;

                                      ○  Risk control procedures, including risk categories, risk statement templates, probability and
                                      impact definitions, and probability and impact matrix; and
                                      ○  Standardized guidelines, work instructions, proposal evaluation criteria, and performance
                                      measurement criteria.
                           •  Closing:

                                      ○  Project closure guidelines or requirements (e.g., lessons learned, final project audits, project
                                      evaluations, product validations, and acceptance criteria).


                      2.1.4.2 corporate Knowledge Base


                         The organizational knowledge base for storing and retrieving information includes, but is not limited to:
                           •   Configuration management knowledge bases containing the versions and baselines of all performing
                              organization standards, policies, procedures, and any project documents;

                           •   Financial databases containing information such as labor hours, incurred costs, budgets, and any project
                              cost overruns;

                           •   Historical information and lessons learned knowledge bases (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 databases containing issue and defect status, control information, issue
                              and defect resolution, and action item results;
                           •   Process measurement databases 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, planned response actions, and
                              defined risk impact).




















             28       ©2013 Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK  Guide) – Fifth Edition
                                                                                          ®


                                           Licensed To: Jorge Diego Fuentes Sanchez PMI MemberID: 2399412
                                       This copy is a PMI Member benefit, not for distribution, sale, or reproduction.
   49   50   51   52   53   54   55   56   57   58   59