Portfolios, Programs, and Projects: What's the Difference?

Understanding the terminology used by organizations when talking about Portfolios, Programs, and Projects is a key requirement for any individual tasked with delivering or contributing to a project in today's working environment.
Course info
Rating
(22)
Level
Beginner
Updated
Jul 28, 2017
Duration
35m
Table of contents
Description
Course info
Rating
(22)
Level
Beginner
Updated
Jul 28, 2017
Duration
35m
Description

All knowledge areas contain a multitude of buzzwords, terminology which you need to quickly grasp and understand in order to work within that knowledge area. In this course, Portfolios, Programs, and Projects: What's the Difference?, you'll quickly and effectively differentiate between three of the most overused and badly used terms within the Project Management industry. First, you'll discover robust "industry standard" definitions of these key terms. Next, you'll explore robust examples supporting those definitions. Finally, the course digs deeper and discusses other key concepts. By the end of this course, you'll be armed with the knowledge required to quickly feel comfortable discussing key Project Management issues.

About the author
About the author

Ben is a Microsoft Project, Project Server/Online consultant, and Data Specialist with over 20 years of implementation experience. He has been a Microsoft MVP for nine years, as well as blogging on various project server scenarios, has articles published on the Microsoft Project User Group (MPUG), and is the author of Microsoft Project 2013 Plain & Simple.

More from the author
More courses by Ben Howard
Section Introduction Transcripts
Section Introduction Transcripts

Course Overview
Hello everyone. My name is Ben Howard, and welcome to this course, which is called Portfolios, Programs, and Projects: What's The Difference? In today's world, organizations are becoming increasingly focused on packaging work into projects, and as this becomes more common there is the requirement to structure these projects into programs, and then programs into portfolios. So, why do we need this structure? Well, it's because, at its purest form, a project is really just an investment in order to effect a change within an organization. And so the organization's management team requires standardized terms and methodologies in order to track the investment and to ensure that the investments deliver their promised benefits. Many projects are run simultaneously and provide solutions or products that are part of a larger common theme, and these common themes often contribute to delivering the organization's strategic goals. The terms program and portfolio are used to help group the projects into these common themes and goals in order to provide the clarity and investment tracking that the management team require. You'll learn, by way of solid definitions and examples, exactly what a project is, what a program is, and what a portfolio is, and how these entities relate to each other. You'll also gain an overview and insight into some of the most common project and portfolio management tools on the market today. At the end of this course you'll be fully conversant with definitions and concepts regarding portfolios, programs, and projects, and you'll be able to classify your work within these structures. I hope you'll join me, Ben Howard, in learning more about these subjects in this course with Pluralsight.