Hooi Nee SauIT Project Manager| ,Kuala Lumpur, Malaysia
Recently, I have discussion with some other PMs. We found that if a project run smoothly(within budget,meet target), the PM role are unable to shine like other roles such as architect, consultant & etc where they make more solid contribution to a project delivery. Senior management unlikely to see the PM contribution and the important of PM role.
We do agree that PM shining in their role & provides contribution to project, if a project has a lot of hiccups & issue escalated to senior management.
I think this is unfair to the PM who put a lot of efforts earlier to do all kind of risk mitigation before it become a project issue.
1. Have you experience the same above?
2. What is your solution and suggestion?
3. In a smooth project, what do you think the PM contribution is?
4. How to make a PM role shining and contributed in company? Saving Changes...
Thanks Rami, obviously the projects that you have managed are completely different than those on which I have worked as a technical consultant. In my projects probably the number of the team members have averaged at around 5 and the stakeholders probably haven't exceeded 20 or maybe 30 at most. But in the IT industry I think it is common for the project teams to be relatively small, unlike construction.
At my present company there is an obsession with project management as any activity that is a little bit out of the scope of the business as usual process needs to be performed as a project and of course a project manager needs to be assigned to it. This has led to the creation of many small simple projects having a single worker and two managers (the project and the program manager).
Not to mention that most of these projects are internal so the "customers" are employees from the same company. In such an environment most project manager don't have the opportunity to shine as they are expected to perform trivial tasks such as reporting and helping the employees working on projects with non-technical issues. You may say that these are not real project managers but I would argue and say that they are but the projects are to simple for them to make use of all of their project management skills.
...
1 reply by Rami Kaibni
Feb 24, 2016 8:47 AM
Rami Kaibni
...
Adrian, thanks s lot for your explanation. Now I have a better understanding of what you were referring to and I totally agree with you. In this case that you've mentioned, there should be one PM handling multiple project or functional manager hamdling a program with multiple related projects with a project coordinator.
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Feb 24, 2016 5:51 AM
Replying to Adrian Carlogea
...
Thanks Rami, obviously the projects that you have managed are completely different than those on which I have worked as a technical consultant. In my projects probably the number of the team members have averaged at around 5 and the stakeholders probably haven't exceeded 20 or maybe 30 at most. But in the IT industry I think it is common for the project teams to be relatively small, unlike construction.
At my present company there is an obsession with project management as any activity that is a little bit out of the scope of the business as usual process needs to be performed as a project and of course a project manager needs to be assigned to it. This has led to the creation of many small simple projects having a single worker and two managers (the project and the program manager).
Not to mention that most of these projects are internal so the "customers" are employees from the same company. In such an environment most project manager don't have the opportunity to shine as they are expected to perform trivial tasks such as reporting and helping the employees working on projects with non-technical issues. You may say that these are not real project managers but I would argue and say that they are but the projects are to simple for them to make use of all of their project management skills.
Adrian, thanks s lot for your explanation. Now I have a better understanding of what you were referring to and I totally agree with you. In this case that you've mentioned, there should be one PM handling multiple project or functional manager hamdling a program with multiple related projects with a project coordinator.
...
1 reply by Adrian Carlogea
Feb 26, 2016 3:56 AM
Adrian Carlogea
...
You're welcome Rami but the reason I know so much about the structure of this organization is because although I am working on contract I have to attend all the staff meetings where all these things are discussed and also there are a bunch of company documents I can read about this.
I work for a structure know as the ICT Division headed by the company's Chief Information Officer. The Division consists of several functional departments who are further divided into teams led by functional team leads and groups of teams led by managers reporting directly to the department's heads.
Each department has its own budget and the functional managers create projects and allocate resources for them. There is also a special department known as the ICT Portfolio Delivery which does not create projects but assists the other departments and the whole ICT Division running their projects. All the project and program managers work for the ICT Portfolio Delivery department which makes project and program management to be a function on its own.
The project managers are non-managerial employees sitting at the bottom of the chart with no direct reports and indirectly reporting to the ICT Portfolio Delivery Manager. I don't know the structure of the department but I think program managers are real managers in the sense that they have direct reports, namely the project managers.
A program manager is responsible for several projects in a program but also each project manager usually manages several projects simultaneously unless he/she is assigned to a more complex project that involves a larger number of stakeholders.
The other divisions of the organization most likely have their own Portfolio Delivery departments who run the Division's projects. Many times however employees from a division are borrowed to work on projects on other divisions.
Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Under the preferred concept of Servant Leadership, the target of the PM is not to shine but to make his team and the customer shine. Then both of them will want to work with you again and your shine will come by time and itself. It is a good example of being humble, supportive and ethical. Be patient and love will come to you.
...
1 reply by Rami Kaibni
Feb 25, 2016 7:09 PM
Rami Kaibni
...
Great Thinking Thomas - I tend to agree with you on this.
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Feb 24, 2016 1:10 PM
Replying to Thomas Walenta
...
Under the preferred concept of Servant Leadership, the target of the PM is not to shine but to make his team and the customer shine. Then both of them will want to work with you again and your shine will come by time and itself. It is a good example of being humble, supportive and ethical. Be patient and love will come to you.
Great Thinking Thomas - I tend to agree with you on this. Saving Changes...
If you want to shine, you must impress people. So your focus should be on them. Don't simply meet their expectations; you want to delight them.
...
1 reply by Hooi Nee Sau
Feb 25, 2016 10:46 PM
Hooi Nee Sau
...
Dear Mr. Parent,
Would you able to share with me an example delight them but not simply meet their expectations? I am wonder if project not meet their expectations, how to delight them? May be there is some soft skill that I not aware about. TQ.
Saving Changes...
Hooi Nee SauIT Project Manager| ,Kuala Lumpur, Malaysia
If you want to shine, you must impress people. So your focus should be on them. Don't simply meet their expectations; you want to delight them.
Dear Mr. Parent,
Would you able to share with me an example delight them but not simply meet their expectations? I am wonder if project not meet their expectations, how to delight them? May be there is some soft skill that I not aware about. TQ. Saving Changes...
Delighting your customer is something that has been around for a few decades, introduced by business gurus like Peter Drucker.
It basically means giving more to the customer than expected. I know it can be counterintuitive in a project where you are measured on costs, time and quality. The trick is in finding ways to deliver more of one, without unduly affecting the other two. This is where innovation, initiative and improvement is needed. Together they will help exceed your client's wants.
Never settle for good enough. You want to be better, if not the best. Saving Changes...
Adrian, thanks s lot for your explanation. Now I have a better understanding of what you were referring to and I totally agree with you. In this case that you've mentioned, there should be one PM handling multiple project or functional manager hamdling a program with multiple related projects with a project coordinator.
You're welcome Rami but the reason I know so much about the structure of this organization is because although I am working on contract I have to attend all the staff meetings where all these things are discussed and also there are a bunch of company documents I can read about this.
I work for a structure know as the ICT Division headed by the company's Chief Information Officer. The Division consists of several functional departments who are further divided into teams led by functional team leads and groups of teams led by managers reporting directly to the department's heads.
Each department has its own budget and the functional managers create projects and allocate resources for them. There is also a special department known as the ICT Portfolio Delivery which does not create projects but assists the other departments and the whole ICT Division running their projects. All the project and program managers work for the ICT Portfolio Delivery department which makes project and program management to be a function on its own.
The project managers are non-managerial employees sitting at the bottom of the chart with no direct reports and indirectly reporting to the ICT Portfolio Delivery Manager. I don't know the structure of the department but I think program managers are real managers in the sense that they have direct reports, namely the project managers.
A program manager is responsible for several projects in a program but also each project manager usually manages several projects simultaneously unless he/she is assigned to a more complex project that involves a larger number of stakeholders.
The other divisions of the organization most likely have their own Portfolio Delivery departments who run the Division's projects. Many times however employees from a division are borrowed to work on projects on other divisions.
...
1 reply by Rami Kaibni
Feb 26, 2016 8:46 AM
Rami Kaibni
...
Then the project manager is basically acting as a project coordinator or expeditor so it should be some kind of weak matrix organization.
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Feb 26, 2016 3:56 AM
Replying to Adrian Carlogea
...
You're welcome Rami but the reason I know so much about the structure of this organization is because although I am working on contract I have to attend all the staff meetings where all these things are discussed and also there are a bunch of company documents I can read about this.
I work for a structure know as the ICT Division headed by the company's Chief Information Officer. The Division consists of several functional departments who are further divided into teams led by functional team leads and groups of teams led by managers reporting directly to the department's heads.
Each department has its own budget and the functional managers create projects and allocate resources for them. There is also a special department known as the ICT Portfolio Delivery which does not create projects but assists the other departments and the whole ICT Division running their projects. All the project and program managers work for the ICT Portfolio Delivery department which makes project and program management to be a function on its own.
The project managers are non-managerial employees sitting at the bottom of the chart with no direct reports and indirectly reporting to the ICT Portfolio Delivery Manager. I don't know the structure of the department but I think program managers are real managers in the sense that they have direct reports, namely the project managers.
A program manager is responsible for several projects in a program but also each project manager usually manages several projects simultaneously unless he/she is assigned to a more complex project that involves a larger number of stakeholders.
The other divisions of the organization most likely have their own Portfolio Delivery departments who run the Division's projects. Many times however employees from a division are borrowed to work on projects on other divisions.
Then the project manager is basically acting as a project coordinator or expeditor so it should be some kind of weak matrix organization.
...
1 reply by Adrian Carlogea
Feb 26, 2016 10:24 PM
Adrian Carlogea
...
I've learn that project coordinator and expediter are part time roles reporting to the functional manager; this is not the case here. At this organization the project manager is a full-time role and all project managers are professionals in the field of project management reporting to one of portfolio department's managers (manager of the project managers).
The functional managers act more like project sponsors but once the project is running I am not sure if they get directly involved in running it. Probably the Portfolio Delivery departments through project and program managers manage the project's budged assigned by the functional manager. I haven't got to know this details yet as for team members that are just doing the work this is not very relevant.
Probably the organization types defined by scholars are just theoretical models and in reality each company uses variations of these models so the organization type may not necessarily be identified against these theoretical models.
Saving Changes...
Khai Ng.IT PMO | IT Project Manager| TTGROUPHanoi, Viet Nam
Hooi described that "Senior management unlikely to see the PM contribution and the important of PM role". He also mentioned that: "PM shining in their role & provides contribution to project, if a project has a lot of hiccups & issue escalated to senior management"
I think the problem is that his Senior Manager. The Senior Manager's narrow mindset created a bad organization culture. Show him that without PM, how people can work together to complete a project. Without PM, a group of very smart people just is a chaotic group; very similar to a company without CEO. Saving Changes...