Post on 25-Aug-2020
Managing Project Portfolios, Programs & Multiple Projects
Russell D. Archibald, FPMI, FAPM, PMPArchibald Associates
IPMA Congress Moscow 2003 Russ Archibald 2
Outline of My Presentation1. The Multi-Project Environment2. Managing Project Portfolios3. Managing Multi-Project Programs4. Managing Multiple Smaller Projects5. Multiproject Operations Planning &
Control6. Summary & Conclusions
IPMA Congress Moscow 2003 Russ Archibald 3
1.The Multiproject Environment
In large organizations, projects must be managed at 3 or 4 levels:
1. Project portfolio level2. Multi-project program level3. ‘Group of minor projects’ level4. Individual major project level
The first 3 of these are discussed here
IPMA Congress Moscow 2003 Russ Archibald 4
Multiproject Environment Characteristics
No organization has totally unlimited resources Competition between and within projects for money, key resources, and management attentionDependencies between projects for the results being produced
IPMA Congress Moscow 2003 Russ Archibald 5
The Basic Multi-Project Management Objective
The multi-project requirements and priorities must be brought together at appropriate levels in the organizationThe basic objective:
To assure that all approved projects are completed to realize the maximum benefits for the entire organization
IPMA Congress Moscow 2003 Russ Archibald 6
Specific Multi-Project Objectives
Complete all projects to meet strategic goals of the organizationSet and manage project priorities for best resource allocation decisionsManage comparative risks proactively
IPMA Congress Moscow 2003 Russ Archibald 7
Specific Multi-Project Objectives (Cont’d)
Provide adequate resources for all projects while assuring their efficient useIntegrate multi-project execution with other ongoing operationsDevelop organizational patterns and management processes for both multi-project and other operations
IPMA Congress Moscow 2003 Russ Archibald 8
2. Managing Project PortfoliosProject portfolio management process
Project Portfolio Steering Group
Relationships between the Steering Group, Project Sponsors, PMO, and Project/Program Managers
IPMA Congress Moscow 2003 Russ Archibald 9
Project to Implement the Portfolio Management Process
Management Project Scope: To design and implement a project portfolio management processThe project team:
Manager, Project Management Office (PMO)PMO staff plus internal/external consultantsSelected project sponsors or other executives
IPMA Congress Moscow 2003 Russ Archibald 10
12 Step Portfolio Mgt. Process1. Define project portfolios needed2. Define project categories that exist
within each portfolio3. Place projects within categories and
programs4. Validate each project with
organization’s strategic objectives
IPMA Congress Moscow 2003 Russ Archibald 11
12 Step Process (Cont’d)
5. Prioritize projects within programs and portfolios
6. Develop Project Portfolio Master Schedule
7. Establish and maintain key resources data bank
8. Allocate available resources to programs and projects in portfolios
IPMA Congress Moscow 2003 Russ Archibald 12
12 Step Process (Cont’d)
9. Compare financial needs with availability10. Decide how to respond to shortfalls11. Plan, authorize and manage each program
and project using the PM process designed for each project category
12. Periodically add or delete, re-prioritize, reallocate resources, & reschedule projects (steps 1 through 12)
IPMA Congress Moscow 2003 Russ Archibald 13
Project Portfolio Steering Group Responsibilities
Approve design and implementation of the PPM ProcessActively participate in process operation
Integrate strategic and project objectivesManage relative project prioritiesApprove new projects for inclusionProvide strategic direction to project sponsors
IPMA Congress Moscow 2003 Russ Archibald 14
Project Portfolio Steering Group Responsibilities (Cont’d)
Recommend to CEO the acquisition of additional financial and other resources when required to support portfoliosRecommend needed improvements in the Project Portfolio Management Process
IPMA Congress Moscow 2003 Russ Archibald 15
Relationships Between the Major Players
Portfolio Steering Group:Give strategic direction on programs & projects to Program/Project Sponsors
Project Sponsors:Give strategic direction & other political, economic, marketing, and technological information to PMO Manager, & affected Program/Project & senior Functional Managers
IPMA Congress Moscow 2003 Russ Archibald 16
Relationships Between the Major Players (Cont’d)
Manager of Project Management (PMO)Communicate strategic direction (priorities, resource decisions, other) to Managers of Programs/Projects without assigned Sponsors, together with affected senior Functional ManagersMay act as Sponsor for such programs and projectsProvide support and guidance on PM
IPMA Congress Moscow 2003 Russ Archibald 17
Relationships Between the Major Players (Cont’d)
Program and Project Managers:Receive strategic direction from Sponsors or the Manager of Project ManagementReceive operational support and professional guidance in planning and control from the PMO/Manager of Project ManagementReflect strategic direction received in their program/project plans and schedulesConvey impact of changes to their Sponsors and/or PMO/Manager of Project Management
IPMA Congress Moscow 2003 Russ Archibald 18
3. Managing Multi-Project Programs
Program: Comprised of 2 or more projects that are interrelated in some fairly direct way
Same product lineCommon strategic objectiveResults from one needed by another
Could be considered a specific portfolio
IPMA Congress Moscow 2003 Russ Archibald 19
Program Versus Project Managers
Similar responsibilities, broader scopeProgram Manager usually supervises 2 or more Project ManagersPrograms usually of longer duration than projects:
Maintaining continuity of responsibility therefore more difficultProgram Manager job is more permanent
IPMA Congress Moscow 2003 Russ Archibald 20
Program Life CyclesComprised of several overlapping project life cyclesTherefore program life cycle may not be well definedProjects are completed, new ones added to the program
IPMA Congress Moscow 2003 Russ Archibald 21
4. Managing Multiple Smaller Projects
Many organizations have few major projects but many smaller onesClassic PM does not apply well to theseOne Project Manager may handle a number of smaller projects, or the Division General Manager may hold the project manager responsibility
IPMA Congress Moscow 2003 Russ Archibald 22
Multiple Major VersusMultiple Small Projects
All projects in one central system
Each project planned & controlled independently
Integrated Planning & Control
Usually in functional depts.
Project Office plus functions
Project Team
Retained in line organization
Project ManagerProject Manager Role
Multiple Small Projects
Multiple Major Projects
IPMA Congress Moscow 2003 Russ Archibald 23
Benefits of Network-Based Systems
Improved planning, scheduling, & resource forecastingDevelopment of planning templatesRe-scheduling with known priority rulesAutomation of schedules and forecasts
IPMA Congress Moscow 2003 Russ Archibald 24
Interdependencies Between and Within Projects1. Result of action
Logical dependencies/interface events
2. Common unit of resourceLogical dependencies/interface events
3. Rate-of-use-of-common-resourcesScheduling with resource leveling
IPMA Congress Moscow 2003 Russ Archibald 25
5. Multi-Project Operations Planning and Control
At master plan and schedule level:Integrates and controls all contracts/projectsFor all functions: marketing, engineering, procurement, manufacturing, & installationFor a product line or operating division
IPMA Congress Moscow 2003 Russ Archibald 26
Centralized Planning & ControlSome companies use a central master planning/operations control function (discussed later)Contracts (projects) flow through functional departments & are planned and controlled centrally
IPMA Congress Moscow 2003 Russ Archibald 28
Key Points:Operations Planning & Control
Interfaces with functional systems at the master schedule levelAvoids detail planned by each functional systemSet of bridging networks links plans through key interface eventsEach contract/project has a network
IPMA Congress Moscow 2003 Russ Archibald 29
Key Points (Cont’d)
Contract/project network plan assembled from templates (fragnets) and modified as needed
Milestone events included for tracking and management reporting
IPMA Congress Moscow 2003 Russ Archibald 30
6. Summary & ConclusionsProjects must be managed at several levels:
Project portfolioMulti-project programGroup of small projects levelIndividual project level
Portfolio project management links strategies to programs & projects
IPMA Congress Moscow 2003 Russ Archibald 31
6. Summary & Conclusions (Cont’d)
Multi-project objectives are different from individual project objectivesPortfolio project management process must be well-designed & properly implementedPortfolio Steering Group, Project Sponsors, Manager of PM, and Program/Project Managers must work together
IPMA Congress Moscow 2003 Russ Archibald 32
6. Summary & Conclusions (Cont’d)
With multiple smaller projects the PM roles can be retained within the line organizationMulti-project/contract Operations Planning and Control System can be the best solution
IPMA Congress Moscow 2003 Russ Archibald 33
6. Summary & Conclusions (Cont’d)
Today’s complex organizations operating in this Internet Age must manage their projects at portfolio, program or multi-project levels — in addition to managing each project as appropriate with classic project management methods
IPMA Congress Moscow 2003 Russ Archibald 34
Thank You For ListeningQuestions?
Rebuttals?
Contact the author:archie@unisono.net.mx