The term Organizational Project Management (OPM) was coined by John Schlichter in May 1998 in a meeting of the Standards Committee of the Project Management Institute. OPM was defined as the execution of an organization’s strategies through projects by combining the systems of portfolio management, program management, and project management. This definition was approved by a team of hundreds of professionals from 35 countries and was published as part of PMI’s Organizational Project Management Maturity Model standard in 2003 and updated later to a second edition in 2008 when it also became an ANSI standard. The standard was updated to a third edition in 2013. The term “Organizational Project Management” should be capitalized because the term is a conventional designation for exactly the systems of processes elaborated in ANSI/PMI 08-004-2008, because it is a proper name for that system and that system is definitive and regimented in its application, and because it does not denote generically any project management that is done in organizations.
According to PMI (2003, 2008, 2013)
Organizational Project Management is the systematic management of projects, programs, and portfolios in alignment with the achievement of strategic goals. The concept of organizational project management is based on the idea that there is a correlation between an organization’s capabilities in project management, program management, and portfolio management and the organization’s effectiveness in implementing strategy.
The Project Management Plan Document also known as Project Plan Document or simply Project Plan is a document that contains the strategy for managing the project and the processes related to all areas of the project (scope, cost, schedule, quality, etc.) which are known as Knowledge Areas according to PMI. There are lots of project management processes mentioned in PMBOK® Guide, but determining what processes need to be used based on the needs of the project which is called Tailoring is part of developing the project management plan
The project plan document may include the following sections:
A High level overview of the project
The roles and authority of team members. It represents the executive summary of the Project Management Plan
The scope statement from the Project charter should be used as a starting point with more details about what the project includes and what it does not include (In-Scope and Out-Of-Scope)
A list of the project Milestones (the stop points that helps evaluating the progress of the project). This list includes the milestone name, a description about the milestone, and the date expected.
WBS which consists of Work Packages and WBS Dictionary, which defines these work packages, as well as Schedule Baseline, which is the reference point for managing project progress, are included here.
This section contains all management plans of all project aspects
Identify key resources needed for the project and their times and durations of need.
This section includes the budgeted total of each phase of the project and comments about the cost.
Acceptable levels of quality.
Some space for the project sponsor to sign off the document