Showing posts with label program manager. Show all posts
Showing posts with label program manager. Show all posts

Friday, May 6, 2011

Chapter 13: Relationship between Project, Program, and Portfolio

So far, we have been talking in terms of projects only. There are two other terms that are closed linked with projects and project management. They are: Program and Portfolio. In this chapter, we are going to look at how these 3 entities are related.

So, lets get started!!!

Relationship between Project, Program and Portfolio:

As a project manager, you should know the basic concepts of program and portfolio and how they are related to each other and to projects. A program may be a part of a higher-level program; it certainly contains some interrelated projects, and it may contain some non-project work as well. Program management focuses on optimally managing the interdependencies among the various projects in the program. The person who manages a program is called the Program Manager.
The program manager’s responsibilities are:

• Prioritize to resolve resource conflict and constraints that affect multiple projects within his program.
• Keep your priorities aligned with the strategic goals and objectives of the organization.
• Resolve issues and manage change within the governance structure of the organization.

Just like a project is managed by a project manager, a program is managed by a program manager, who oversees the projects and provides high-level guidance to the project managers. In other words, a program manager oversees projects and coordinates efforts between projects but does not manage the projects.

Why is that?

That is because; we the project managers are managing our projects!!!

A portfolio contains both programs and projects and is managed by a portfolio manager. The portfolio is drawn directly from the strategic business plan of the organization.
The strategy of an organization is an action plan to achieve its business goals and objectives. It’s also called a strategic plan or a strategic business plan. The strategy determines the portfolio of projects and programs that the organization will execute. A portfolio is a set of projects, programs, or both that is managed in a coordinated fashion to obtain control and benefits not available from managing them individually.

What is Portfolio Management?

Portfolio management is the centralized management of one or more portfolios, and it includes identifying, prioritizing, authorizing, managing, and controlling projects, programs, and other related work in order to obtain specific strategic business objectives of the organization. Just as a program is managed by a program manager, a portfolio is managed by a portfolio manager.
To understand the relationship between these 3 entities, projects, programs and portfolios we need to understand that:

• If an organization does not have any programs but has only individual projects, all these projects can be grouped into one or more portfolios.
• If an organization has programs and no individual project external to all programs, all these programs can be grouped into one or more portfolios.
• If an organization has some programs and some individual projects, all these programs and projects can be grouped into one or more portfolios.

Portfolio management focuses on making sure that programs and projects are prioritized for resources to serve the organization’s strategy. In simpler terms, a portfolio manager worries about the success of the whole strategy put forth by the organization rather than the success of a single project (like what we do)

Therefore, investment decisions are usually made at the portfolio level. Program management focuses on achieving the benefits that would be aligned with the portfolio and hence with the strategic objectives of the organization. So, a portfolio is part of the interface between the programs and strategic business objectives of the organization for which the programs are run.

The relationship between these 3 entities is better explained by the picture below:


As you can see in the picture above, a portfolio is composed of projects, programs or both. And a program consists only of projects.

When compared to projects and programs, a portfolio is closer to an organization’s business objectives, and therefore this is where most of the investment decisions are made.
It’s also important to note that an operation is not part of a project. However, a program can include a non-project work. Similarly, a portfolio can also include work that is not included in any of its constituent projects and programs.

Let us wrap up this chapter with a comparison between projects, programs and portfolios.

Comparison between a Project, a Program, and Portfolio



Previous: Environmental Factors & Process Assets

Next: Other Terms Related to Project Management

Wednesday, May 4, 2011

Chapter 8: Project Stakeholders

In the previous chapters, we have been using the term Project Stakeholders repeatedly and we havent had any clear cut definition or description as to who these people are. Well, you need to look no further, we are going to do it right away in this chapter.

So, lets get started!!!

Who are the Project Stakeholders?

Project stakeholders are individuals and organizations whose interests are affected (positively or negatively) by the project execution and completion. In other words, a project stakeholder has something to gain from the project or lose to the project. Accordingly, the stakeholders fall into two categories—positive stakeholders, who will normally benefit from the success of the project, and negative stakeholders, who see some form of disadvantage coming from the project. The implications obviously are that the positive stakeholders would like to see the project succeed and the negative stakeholder’s would be happy if the project was delayed or even better cancelled.

For ex: let us say, your state government wants to build a Government Hospital in your city. It is a good thing right? You, the citizens of your city and the chief minister are all positive stakeholders of this project. Lets say there is a private Hospital in the city that is having a thriving business currently. They would be negative stakeholders because, if the government hospital comes up, their business will be affected and hence they would be happy if the government scraps its project.

Negative stakeholders are often overlooked by the project manager and the project team, which increases the project risk. Ignoring positive or negative project stakeholders will have a damaging impact on the project. Therefore, it’s important that you, as the project manager, start identifying the project stakeholders early on in the project. The different project stakeholders can have different and conflicting expectations, which you need to analyze and manage.

Identifying Project Stakeholders

Identifying all the project stakeholders might be a difficult task, but the following are the obvious stakeholders in any project:

1. Project manager - Include yourself first. The project manager in charge of the project, in the list of the stakeholders to start with.
2. Project management office (PMO) - If your organization has a PMO, and it is directly or indirectly responsible for the outcome of a project, then the PMO is a stakeholder in that project.
3. Project team - This team consists of the project manager, the project management team, and the individuals who perform the work of the project to produce the project outcome. This team may consist of individuals from different groups and departments with different subject matter expertise and skills.
4. Program manager - If your project is part of a program, then the program manager is certainly a stakeholder of your project.
5. Portfolio managers - A portfolio manager is an individual who performs high-level management (governance) of a set of projects or programs and interfaces between the projects/programs and the business strategy of the organization for which the projects and programs are being run.
6. Portfolio review board - A portfolio review board is a committee that selects and rejects the projects by reviewing them for factors such as the project value, return on investment, and risks involved in performing the project.
7. Functional managers - These are the individuals who play the management roles within administrative or functional areas of the organization. For example, the VP of marketing is a functional manager and so is the director of engineering. The level of authority depends on their position in the hierarchy and also the organizational structure. For example, if you are using resources that are under a functional manager, that functional manager is a stakeholder of your project.
8. Operational management - These are the individuals who are performing management roles in the operational areas of the organization. For example, the director of IT, who is responsible for maintaining the computer network that your team is using, is a stakeholder in your project. Depending on your project, you might be handing over the product of the project to an operations group that will be responsible for providing the long-term support for it.
9. Sellers – Sellers are entities external to the performing organization, such as contractors and suppliers, who enter into a contractual agreement with the performing organization to provide certain components for the project. These components are the products, services, or results that you procure.
10. Business Partners - Business partners are the external organizations that fill a specific role for the project, such as installing the product of the project, providing training and support for the product, or providing specialized expertise for the project. Business partners are different from vendors in that they have a special ongoing relationship with the organization, which sometimes is attained by satisfying some requirements, such as certifications.
11. Customer/user - In general, customers are the entity that will acquire the project’s outcome, such as product, and users are the entity that will use the product. In some cases the customers and users may be the same entity, and in other cases there may be a whole chain (with different layers) of customers and users.
12. Project sponsor - This is the individual or group that provides financial resources for the project. A sponsor has a major stake in the project and may perform an active role in the project team from time to time.

Following are some of the functions of a sponsor:

1. The sponsor champions the project when it’s conceived. This includes gathering support for the project by performing actions such as acting as project spokesperson to the higher-level management and spelling out the benefits of the project.
2. The sponsor leads the project through the selection process until the project is finally authorized, at which point the leadership role goes to the project manager.
3. The sponsor plays an important role in developing the initial project scope and charter.
4. The sponsor serves as an authority and a catalyst for issues beyond the control of project managers, such as authorizing some critical changes and other yes/no decisions.

Identifying Other Stakeholders

We have just identified the easy bunch of stakeholders that every project would have. In addition to these key stakeholders, who are easy to identify, there can be a number of other stakeholders, who might be more difficult to identify, inside and outside your organization. Depending upon the project, these might include investors, sellers, contractors, family members of the project team members, government agencies, media outlets, lobbying organizations, individual citizens, and a whole myriad of other individuals who might have an interest in this project and its outcome.

While dealing with the stakeholders, the keyword is influence. Watch out for influencers who are not direct customers or users of the product or service that will come from the project, but who can influence the course of the project due to their position in the customer organization or the performing organization. The influence can be positive or negative.

So, not only are the stakeholders affected positively and negatively by the project, but the project can also be impacted positively or negatively by them. It is critical for the success of the project that you identify positive and negative stakeholders early on in the project, understand and analyze their varying and conflicting expectations, and manage those expectations throughout the project.

Trivia:

Do not confuse the project management team with the project team. The project management team consists of individuals involved in the project management tasks. It is a subset of the project team, which includes the members of the project management team and also other members, such as those who perform the actual work of the project.

In the next chapter, we shall take a look at one of the most important and influential stakeholder in any project. The person who can make or break the project.

Previous: Project Management Knowledge Areas

Next: The Most Influential Stakeholder
© 2013 by www.getpmpcertified.blogspot.com. All rights reserved. No part of this blog or its contents may be reproduced or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission of the Author.

Followers

Popular Posts