Close Project – finalizing all activities across all of the Project Management

• Organizational corporate knowledge base for storing and retrieving information: ♦ Process measurement database used to collect and make available measurement data on processes and products ♦ Project files e.g., scope, cost, schedule, and quality baselines, performance measurement baselines, project calendars, project schedule network diagrams, risk registers, planned response actions, and defined risk impact 4 ♦ Historical information and lessons learned knowledge base e.g., project records and documents, all project closure information and documentation, information about both the results of previous project selection decisions and previous project performance information, and information from the risk management effort ♦ Issue and defect management database containing issue and defect status, control information, issue and defect resolution, and action item results ♦ Configuration management knowledge base containing the versions and baselines of all official company standards, policies, procedures, and any project documents ♦ Financial database containing information such as labor hours, incurred costs, budgets, and any project cost overruns.

4.1.2 Develop Project

Charter: Tools and Techniques .1 Project Selection Methods Project selection methods are used to determine which project the organization will select. These methods generally fall into one of two broad categories 4 : • Benefit measurement methods that are comparative approaches, scoring models, benefit contribution, or economic models. • Mathematical models that use linear, nonlinear, dynamic, integer, or multi- objective programming algorithms. .2 Project Management Methodology A project management methodology defines a set of Project Management Process Groups, their related processes and the related control functions that are consolidated and combined into a functioning unified whole. A project management methodology may or may not be an elaboration of a project management standard. A project management methodology can be either a formal mature process or an informal technique that aids a project management team in effectively developing a project charter. A Guide to the Project Management Body of Knowledge PMBOK ® Guide Third Edition 2004 Project Management Institute, Four Campus Boulevard, Newtown Square, PA 19073-3299 USA 85 .3 Project Management Information System The Project Management Information System PMIS is a standardized set of automated tools available within the organization and integrated into a system. The PMIS is used by the project management team to support generation of a project charter, facilitate feedback as the document is refined, control changes to the project charter, and release the approved document. .4 Expert Judgment Expert judgment is often used to assess the inputs needed to develop the project charter. Such judgment and expertise is applied to any technical and management details during this process. Such expertise is provided by any group or individual with specialized knowledge or training, and is available from many sources, including: • Other units within the organization • Consultants • Stakeholders, including customers or sponsors • Professional and technical associations • Industry groups.

4.1.3 Develop Project Charter: Outputs

.1 Project Charter Described in the introduction to Section 4.1.

4.2 Develop Preliminary Project Scope Statement

The project scope statement is the definition of the project—what needs to be accomplished. The Develop Preliminary Project Scope Statement process addresses and documents the characteristics and boundaries of the project and its associated products and services, as well as the methods of acceptance and scope control. A project scope statement includes: • Project and product objectives • Product or service requirements and characteristics • Product acceptance criteria • Project boundaries • Project requirements and deliverables • Project constraints • Project assumptions • Initial project organization • Initial defined risks • Schedule milestones • Initial WBS • Order of magnitude cost estimate • Project configuration management requirements A Guide to the Project Management Body of Knowledge PMBOK ® Guide Third Edition 86 2004 Project Management Institute, Four Campus Boulevard, Newtown Square, PA 19073-3299 USA • Approval requirements. The preliminary project scope statement is developed from information provided by the initiator or sponsor. The project management team in the Scope Definition process further refines the preliminary project scope statement into the project scope statement. The project scope statement content will vary depending upon the application area and complexity of the project and can include some or all of the components identified above. During subsequent phases of multi-phase projects, the Develop Preliminary Project Scope Statement process validates and