A project management office (usually abbreviated to PMO) is a group or department within a business, government agency, or enterprise that defines and maintains standards for project management within the organization. The PMO strives to standardize and introduce economies of repetition in the execution of projects. The PMO is the source of documentation, guidance, and metrics on the practice of project management and execution.
Darling & Whitty (2016) note that the definition of the PMO's function has evolved over time:
Often, PMOs base project management principles on industry-standard methodologies such as PRINCE2 or guidelines such as PMBOK. [2]
There are many reasons for project failures. According to a PricewaterhouseCoopers survey [3] of 1,524 organizations, inadequate project estimating and planning constitutes 30% of project failures, lack of executive sponsorship constitutes 16%, and poorly defined goals and objectives constitutes 12%. It also found that using established project management approaches increased success as measured by a project's key performance indicators of quality, scope, schedule, budgets and benefits. The survey indicates that operating an established PMO is one of the top three factors that drive successful project delivery. [3]
Darling & Whitty (2016) found that there is a complexity of interconnections in PMO intellectual capital, and though often the rationale for PMO establishment is to enhance stakeholder satisfaction with projects, often the establishment of the PMO leads to significant dissatisfaction in senior management. [1]
A PMO may have other functions beyond standards and methodology, and may participate in strategic project management either as a facilitator or owner of the Portfolio Management process. Tasks [4] may include monitoring [5] and reporting [6] on active projects and portfolios [7] (following up project until completion) and reporting progress to top management for strategic decisions on what projects to continue or cancel.
The degree of control and influence that PMOs have on projects depends on the type of PMO. The three general types are:
There are many opinions about what practices PMOs must fulfill. The PMBoK 5th edition dedicates a page and a half to such discussion, identifying 6 PMO functions. Hobbs & Aubry (2010) identify 27 distinct functions of PMOs, highlighting a number of these that were found to not correlate with enhanced project performance. Darling & Whitty (2016) state there is a need for evidence-based management practice, that consultants and practitioners are providing unproven solutions in which organizations both public and private are investing enormous quantities of finance without assured outcome. The publication of opinions without scientific basis in the field of science, medicine or law would not be tolerated, and it is equally important for justification to be presented in the management field. [1]
Some PMOs operate in specialist contexts. In the Scaled Agile Framework the term APMO is used to define a PMO with a focus on supporting business agility.
PMO departments change frequently and for a variety of reasons. Research indicates that changes to portfolio management and methods, collaboration and accountability; project management maturity and performance; and work climate are all factors that drive PMO change. [8]
Whilst PMO functions change through frequent transformations, it is argued that the core function of the PMO is to act as a catalyst for change and delivery within organizations. [9] [10]
There are a range of PMO types, including: [11]
The Project Management Institute (PMI) Program Management Office Community of Practice (CoP) describes the PMO as a strategic driver for organizational excellence, which seeks to enhance the practices of execution management, organizational governance, and strategic change leadership. [13]
Darling & Whitty (2016) highlight that many PMO typologies have existed, from the early 1800s as a collective for running government strategy in the agricultural sector, to the civil infrastructure projects of the early 20th century, to the early 2000s when the PMO became a commodity to be traded upon. It would be impossible to group PMOs into specific types (Darling & Whitty, 2016). [1]
Whilst the 'P' in PMO usually stands for "project," it can also refer to "program" or "portfolio." Where project management offices support projects, program management offices have a broader remit including getting and sustaining the benefits from projects/programs. Portfolio management offices have the added responsibility of supporting organizations in achieving strategic goals [14]
{{cite news}}
: CS1 maint: multiple names: authors list (link)Earned value management (EVM), earned value project management, or earned value performance management (EVPM) is a project management technique for measuring project performance and progress in an objective manner.
Project management is the process of supervising the work of a team to achieve all project goals within the given constraints. This information is usually described in project documentation, created at the beginning of the development process. The primary constraints are scope, time, and budget. The secondary challenge is to optimize the allocation of necessary inputs and apply them to meet pre-defined objectives.
A project is a type of assignment, typically involving research or design, that is carefully planned to achieve a specific objective.
A project manager is a professional in the field of project management. Project managers have the responsibility of the planning, procurement and execution of a project, in any undertaking that has a defined scope, defined start and a defined finish; regardless of industry. Project managers are first point of contact for any issues or discrepancies arising from within the heads of various departments in an organization before the problem escalates to higher authorities, as project representative.
Program management is the process of managing several related projects, often with the intention of improving an organization's performance. It is distinct from project management.
The Project Management Institute is a U.S.-based not-for-profit professional organization for project management.
Project stakeholders are persons or entities who have an interest in a given project. According to the Project Management Institute (PMI), the term project stakeholder refers to "an individual, group, or organization, who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio. ISO 21500 uses a similar definition.
In organizational studies, resource management is the efficient and effective development of an organization's resources when they are needed. Such resources may include the financial resources, inventory, human skills, production resources, or information technology (IT) and natural resources.
Enterprise Project Management, in broad terms, is the field of organizational development that supports organizations in managing integrally and adapting themselves to the changes of a transformation. Enterprise Project Management is a way of thinking, communicating and working, supported by an information system, that organizes enterprise's resources in a direct relationship to the leadership's vision and the mission, strategy, goals and objectives that move the organization forward. Simply put, EPM provides a 360 degree view of the organization's collective efforts.
A risk management plan is a document that a project manager prepares to foresee risks, estimate impacts, and define responses to risks. It also contains a risk assessment matrix. According to the Project Management Institute, a risk management plan is a "component of the project, program, or portfolio management plan that describes how risk management activities will be structured and performed".
A business case captures the reasoning for initiating a project or task. Many projects, but not all, are initiated by using a business case. It is often presented in a well-structured written document, but may also come in the form of a short verbal agreement or presentation. The logic of the business case is that, whenever resources such as money or effort are consumed, they should be in support of a specific business need. An example could be that a software upgrade might improve system performance, but the "business case" is that better performance would improve customer satisfaction, require less task processing time, or reduce system maintenance costs. A compelling business case adequately captures both the quantifiable and non-quantifiable characteristics of a proposed project. According to the Project Management Institute, a business case is a "value proposition for a proposed project that may include financial and nonfinancial benefit."
Project Management Professional (PMP) is an internationally recognized professional designation offered by the Project Management Institute (PMI). As of 31 July 2020, there are 1,036,368 active PMP-certified individuals and 314 chartered chapters across 214 countries and territories worldwide.
A federal enterprise architecture framework (FEAF) is the U.S. reference enterprise architecture of a federal government. It provides a common approach for the integration of strategic, business and technology management as part of organization design and performance improvement.
Project portfolio management (PPM) is the centralized management of the processes, methods, and technologies used by project managers and project management offices (PMOs) to analyze and collectively manage current or proposed projects based on numerous key characteristics. The objectives of PPM are to determine the optimal resource mix for delivery and to schedule activities to best achieve an organization's operational and financial goals, while honouring constraints imposed by customers, strategic objectives, or external real-world factors. Standards for Portfolio Management include Project Management Institute's framework for project portfolio management, Management of Portfolios by Office of Government Commerce and the PfM² Portfolio Management Methodology by the PM² Foundation.
IT portfolio management is the application of systematic management to the investments, projects and activities of enterprise Information Technology (IT) departments. Examples of IT portfolios would be planned initiatives, projects, and ongoing IT services. The promise of IT portfolio management is the quantification of previously informal IT efforts, enabling measurement and objective evaluation of investment scenarios.
Total cost management (TCM) is the name given by AACE International to a process for applying the skills and knowledge of cost engineering. It is also the first integrated process or methodology for portfolio, program and project management. It was initially conceived by Thomas D. Fromm and John Nunnemaker of Perkins & Will, architects, in 1990 to apply to the design of the University of Illinois Life and Science Building and was presented as a concept to the Society of University and College Planners (SCUP) the following year. AACE first introduced the concept in the 1990s and published the full presentation of the process in the "Total Cost Management Framework" in 2006.
A glossary of terms relating to project management and consulting.
Benefits realization management (BRM), also benefits management, benefits realisation or project benefits management, is a project management methodology, often visual, addressing how time and resources are invested into making desirable changes. BRM is used to manage the investment by organizations in procurement, projects, programmes and portfolios, and has been shown to increase project success across different countries and industries.
The following outline is provided as an overview of and topical guide to project management:
ISO 21500, Guidance on Project Management, is an international standard developed by the International Organization for Standardization, or ISO starting in 2007 and released in 2012. It was intended to provide generic guidance, explain core principles and what constitutes good practice in project management. The ISO technical committee dealing with project management, ISO/PC 236 was held by the American National Standards Institute (ANSI) which had approved four standards that used Project Management Institute (PMI) materials, one of which was ANSI/PMI 99-001-2008, A Guide to the Project Management Body of Knowledge - 4th Edition.
{{cite book}}
: CS1 maint: location missing publisher (link)