PM Perspectives Research Group
NOT REGISTERED? SIGN-UP HERE
Project Management Perspectives

Applying Single-Project Management Knowledge in Project Program Context

PDF Download
Posted: 11-Apr-2013 | View Highlights | Learning Toolkit |  Bookmark / Share This Article


In today's hyper business environment, organizations must develop new products and services quickly, before their market disappears. Frequently, this requires managing several ongoing inter-related projects at the same time, known as project program management.

Researcher Mihaly Görög of Corvinus University of Budapest in Hungary set out to discover how single-project management tools can be applied to program management in order to improve efficiencies.

He studied completed project programs and their associated projects in six companies, all from different industries. He interviewed key management executives, project and program managers, sponsors and team members.

He examined the six project programs to determine their organizational framework, scope, implementation plans, resource allocation, cost estimations and controls.

Görög also studied the problems that these organizations encountered as they executed their projects and project programs, such as

• Decision-making
• Coordination
• Scope definition and change-management
• Project control
• Planning (scheduling, resource allocation, cost estimation)

From these findings, Görög developed a more comprehensive definition for determining whether a collection of inter-related projects is actually a project program.

"A project program is more than a group of projects," says Görög. Besides the common underlying strategic objective, he says, "we identified two specific inter-relationships that transform a group of projects into a project program - resource-related and scope-related interdependence."

He defines resource-related interdependence as the common resources required to implement the program, and scope-related interdependence as the reliance of one program-project outcome on the outcomes of other program projects, and vice versa.

He found that the following project-management tools are useful for single projects, and examined how these were applied in the context of the six project programs:

• organizational arrangements - decision-making and coordination
• project implementation plans (especially the task-responsibility matrix) - coordination and resource allocation
• project control (i.e. both scope and process control) - decision- making, change management, and monitoring
• structural plans (i.e., capability-breakdown structure and product-breakdown structure) (see footnote 1) - scope definition and change management

He found that applying single-project management tools is most effective when:

• a program's projects are connected by resource-related interdependence (interrelationships). "The program-level use of the resource-allocation tools and the so-called double scheduling (see footnote 2) then become very important," he says, to avoid resource congestion as demand escalates during program implementation.

• a program's projects are connected by scope-related interdependence (interrelationships). "In this case, the program strategy becomes very important," he says. "It is difficult but critical to define the scope of the expected program result and the associated scope of the project results."

Görög concludes that "program management is not scaled-up project management," and says that single-project management tools can play a decisive role in overcoming the principal problems encountered in project programs.

Footnotes:
1) The capability-breakdown structure supports the strategy-oriented scope definition by identifying the required functional and non-functional capabilities of the desired project result. The product-breakdown structure revealed the means (technical solution, built-in materials, etc.) for realizing the required capabilities

2) Double scheduling: The first step is scheduling each project based on its own precedent relationships characteristic of the project in question. Then the program's projects should be scheduled in order to avoid resource congestion during program implementation

 

Source: Görög, M. "Translating single project management knowledge to project programs", Project Management Journal, 42:2, March 2011, pp.17-31.

PMPerspectives.org is a website which connects project managers and sponsors with project management researchers. Our mission is to understand and improve projectmanagement practices. The research team comprises Dr. Blaize Horner Reich and Dr. Andrew Gemino from Simon Fraser University, Canada and Dr. Chris Sauer from Oxford University, UK.

© Reich, Gemino, Sauer (2012) 

This article was reposted in 2013 with minor typographic corrections. 




What challenges have you encountered in your project programs?

Respond  Read Responses
What effective single-project management tools have you applied in a project-program context?

Respond  Read Responses


Does Size Really Matter?
highlights | full version | pdf | Learning Toolkit
Delivering Business Value from IT Projects – Results from a Pilot Study
highlights | full version | pdf | Learning Toolkit
Improve Project Success Rate Using Three Lenses
highlights | full version | pdf | Learning Toolkit
Identifying and Acting on Early Warning Signs in Complex Projects
highlights | full version | pdf | Learning Toolkit
The Thought-Leader Mindset
highlights | full version | pdf | Learning Toolkit
IT Projects: Getting Beyond CHAOS
highlights | full version | pdf | Learning Toolkit
Decision-Making in Agile Project Teams
highlights | full version | pdf | Learning Toolkit
Do Women Perform Better than Men?
highlights | full version | pdf | Learning Toolkit
Building The PM-Centric Organization
highlights | full version | pdf | Learning Toolkit
Balancing Structure with Agility Offers Best of Both Worlds
highlights | full version | pdf | Learning Toolkit
Managing Great Expectations
highlights | full version | pdf | Learning Toolkit
Know Your Knowledge Risks
highlights | full version | pdf | Learning Toolkit
Managing Knowledge Risks
highlights | full version | pdf | Learning Toolkit
Applying Lessons Learned to a Project
highlights | full version | pdf | Learning Toolkit
Igniting the Passion - What Motivates Project Managers?
highlights | full version | pdf
Improve your Megaproject’s Briefing Process with Collaborative Briefing
highlights | full version | pdf
Accidental Project Managers Not a Myth in the Public Sector
highlights | full version | pdf
Managing for Collective Competence in Public-Private Partnerships
highlights | full version | pdf
Supporting Successful Cooperation in Public-Private Partnerships
highlights | full version | pdf
Motivating Agile Teams
highlights | full version | pdf
New Research on Effecting Change in the Organization
highlights | full version | pdf
PMP Certification Undervalued in IT Industry
highlights | full version | pdf
Superior Project Managers
highlights | full version | pdf
Innovations Improving IT Project Performance
highlights | full version | pdf
Personality Plus: Choosing the Best Fit for Your Software Project
highlights | full version | pdf
Study links good leaders to successful projects
highlights | full version | pdf
Sponsors Play a Vital Role in Projects
highlights | full version | pdf
New Roles for the Consultant Project Manager
highlights | full version | pdf
Measuring for Success in IT Projects
highlights | full version | pdf
The New Project Leader
highlights | full version | pdf
Planning for the Unexpected
highlights | full version | pdf

  • Home
  • FAQ
  • Links
  • Articles RSS
  • Sitemap
  •  
Site Last Updated: 11-May-2013
Oxford University Simon Fraser University © 2013 PM Perspectives | Supported By Grants From The Social Sciences & Humanities Research Council Of Canada
604 Media - Vancouver Web Design