Project Management Central

Please login or join to subscribe to this thread

Topics: Organizational Project Management, PMI Standards
Can business operations be considered a part of a Program?
Anonymous
Consider a business with a long term contract to deliver a product and associated services. Phase 1 of the contract is build and manufacture of the product and Phase 2 is the operations and maintenance. The contract is a fixed Term so it has a defined start and finish date so many would consider it a project. However, since Phase 2 makes up the majority of the duration of the contract, it seems like the project/program should end at phase 1 and the entire contract would NOT be considered a Program and more suitably categorized as a Portfolio since it encompasses all of the items that align to the businesses strategic goals. Seeking a perspective from others.
Sort By:
Network:54



No, as a program is a collection of projects where a project is temporary in that it has a defined beginning and end in time, and therefore defined scope and resources as per PMP.
Operations and maintenance are considered as BAU activities and cannot be considered as projects.
So 2 contracts :
Phase 1 : project
Phase 2 : Maintenance contract
This is my point of view on this
Network:238



This is a very good question. Lack of understanding can cause this to happen fact is that it cannot and should not be considered part of a program. The main issue is making sure to separate Hand offs and Post delivery support which comes after the deliverable. ( no wonder PMPs are sort after ) from an EPM stand point a business case, project charter.cannot be made for an operation. i can go on and on about this.
...
1 reply by Thomas Walenta
Apr 19, 2019 5:41 AM
Thomas Walenta
...
Ephraim,
you are right for a project, the question is about a program though. These are 2 different animals:
https://www.slideshare.net/walenta/ipma-wo...-panama-walenta
Network:17



It may help to view it from an agile perspective. In scrum you're supporting a Product over a project and so the maintenance period is the iterative period where you're getting feedback, making the product better, and supporting it while it is live.
...
1 reply by Thomas Walenta
Apr 21, 2019 6:27 AM
Thomas Walenta
...
@Grace, agree, if the product is continuously improved and updated, it might even be a good application for DevOps.

The question though asked about a phased approach, phase 1 being development and phase 2 being maintenance. This approach is taken with big complex developments where there is a significant cost difference between developers and maintenance people, and the latter are often outsourced to low-cost areas. Also, maintenance includes another type of work (debugging, user Q&A, working under SLA with tight solution times) which many high-skilled developers dislike.
Network:221



I would generally agree with the above, however not all projects/programs end at delivery and there can be discrete planned maintenance and operations projects which are part of the same program. Although post-delivery, they can still be related to the original development, serve the same objective, and have interdependent plans.

For example there could be operator training required and discrete maintenance projects such as a major overhaul after a defined period of operation that fall under the same program. I see those as exceptions however.
Network:2251



Yes, they can and they often do.

I ran a program with multiple country SAP rollouts and drew in operations (datacenter and application maintenance) into my program to better coordinate changes and give the client a consistent view.
Olympic games include the 3 weeks of actually operating the games.

Both PMI and Axelos program standards state that a program can include 'activities' other than projects, if they are needed to deliver the expected benefits. Operations can be such activities.
Network:2251



Apr 18, 2019 12:03 PM
Replying to Ephraim Atari
...
This is a very good question. Lack of understanding can cause this to happen fact is that it cannot and should not be considered part of a program. The main issue is making sure to separate Hand offs and Post delivery support which comes after the deliverable. ( no wonder PMPs are sort after ) from an EPM stand point a business case, project charter.cannot be made for an operation. i can go on and on about this.
Ephraim,
you are right for a project, the question is about a program though. These are 2 different animals:
https://www.slideshare.net/walenta/ipma-wo...-panama-walenta
Network:2251



Apr 18, 2019 4:46 PM
Replying to Grace Kilpatrick
...
It may help to view it from an agile perspective. In scrum you're supporting a Product over a project and so the maintenance period is the iterative period where you're getting feedback, making the product better, and supporting it while it is live.
@Grace, agree, if the product is continuously improved and updated, it might even be a good application for DevOps.

The question though asked about a phased approach, phase 1 being development and phase 2 being maintenance. This approach is taken with big complex developments where there is a significant cost difference between developers and maintenance people, and the latter are often outsourced to low-cost areas. Also, maintenance includes another type of work (debugging, user Q&A, working under SLA with tight solution times) which many high-skilled developers dislike.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"If I had no sense of humor, I would long ago have committed suicide."

- Mahatma Gandhi

ADVERTISEMENT

Sponsors