2007•Industrial and Commercial TrainingRequires access

Development of project management systems

Anthony Eve

Open publisher page 31 citations

Abstract

Purpose The purpose of this paper is to highlight the need for organizations to synchronize the development of the complete project management system. Design/methodology/approach The paper concentrates on the three key areas of development for the project management system, “what we do”, “when we do it” and “how we do it”. The paper further looks at these key elements in conjunction with an organization's project management maturity, defines the typical components of the project management system and how organizations can measure improved project management effectiveness to their bottom line performance. The paper concludes with a high level prescription for developing a project management system. Findings The paper identifies the cost of not synchronizing efforts in developing the project management system. It demonstrates how large investments are not maximized when individual elements of the project management system are developed separately. Practical implications The is paper highlights the need to establish near, mid and long term change plans, or road maps, which under the control of senior management define the development of all aspects of the project management system. Originality/value This paper looks at the organization support required to develop successful project management systems and relates this with measuring project management maturity and the impact to bottom line performance. This paper has relevance to CEO's, CFO's, HR directors and senior executives who have responsibility for developing project management who need to transition their organizations project based.

About this research paper

What this paper is about

Purpose The purpose of this paper is to highlight the need for organizations to synchronize the development of the complete project management system. Design/methodology/approach The paper concentrates on the three key areas of development for the project management system, “what we do”, “when we do it” and “how we do it”. The paper further looks at these key elements in conjunction with an organization's project management maturity, defines the typical components of the project management system and how organizations can measure improved project management effectiveness to their bottom line performance. The paper concludes with a high level prescription for developing a project management system. Findings The paper identifies the cost of not synchronizing efforts in developing the project management system. It demonstrates how large investments are not maximized when individual elements of the project management system are developed separately. Practical implications The is paper highlights the need to establish near, mid and long term change plans, or road maps, which under the control of senior management define the development of all aspects of the project management system. Originality/value This paper looks at the organization support required to develop successful project management systems and relates this with measuring project management maturity and the impact to bottom line performance. This paper has relevance to CEO's, CFO's, HR directors and senior executives who have responsibility for developing project management who need to transition their organizations project based.

Why it matters

OpenAlex reports 31 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

Purpose The purpose of this paper is to highlight the need for organizations to synchronize the development of the complete project management system. Design/methodology/approach The paper concentrates on the three key areas of development for the project management system, “what we do”, “when we do it” and “how we do it”. The paper further looks at these key elements in conjunction with an organization's project management maturity, defines the typical components of the project management system and how organizations can measure improved project management effectiveness to their bottom line performance. The paper concludes with a high level prescription for developing a project management system. Findings The paper identifies the cost of not synchronizing efforts in developing the project management system. It demonstrates how large investments are not maximized when individual elements of the project management system are developed separately. Practical implications The is paper highlights the need to establish near, mid and long term change plans, or road maps, which under the control of senior management define the development of all aspects of the project management system. Originality/value This paper looks at the organization support required to develop successful project management systems and relates this with measuring project management maturity and the impact to bottom line performance. This paper has relevance to CEO's, CFO's, HR directors and senior executives who have responsibility for developing project management who need to transition their organizations project based.

Key concepts: Project management triangle, OPM3, Project management, Process management, Project charter, Extreme project management, Project planning, Program management

Related papers

Back to paper searchBrowse research topicsOriginal source
Development of project management systems — Research Paper | ScholarLens