Portfolio and Program Management: Harmony or Conflict? |
||||||||||||||||||||||||||||||||||||
|
|
Home > Articles >
When I first started managing projects there were simply project managers. We knew what had to be delivered and we delivered it to the best of our abilities. Soon after, PMOs came along to add structure to the way that our projects were managed, to standardize processes and tools and to centralize reporting. After that, program management recognized that many projects were related and needed to be managed as parts of the whole--not just from an approach and tools standpoint, but effectively as one large scale initiative.
Now portfolio management builds on that to take a company-wide view of all the projects that are underway--and to ensure that we leverage organizational resources to maximum efficiency regardless of their specific deliverables. Can that function successfully co-exist with the concept of a program-based organization that requires us to look at our projects in terms of common deliverables? Or is it a recipe for contradictory approaches and perspectives as we struggle to look at the same collection of projects in different groupings?
Why we need portfolio management
Portfolio management is the closest that we get to a corporate view of our projects.
Please login/register to read the entire article.
sponsored announcements and special offers
Build and deploy interactive reports and dashboards — without any hidden costs. Our in-the-cloud free trial lets you see for yourself — no download required. SAP Crystal Reports Server 60-day Free Trial
Improve your company's efficiency and effectiveness, no matter its size. Download the SAP whitepaper Business Intelligence: The Definitive Guide for Mid-Size Organizations.
Online Lean Six Sigma Certificates
Online Project Mgmt Certificates
|
| ||||||||||||||||||||||||||||||||||