Prem KumarSr. Project Leader| Corent Technologies IncChennai, Tamil Nadu, India
How far technical knowledge will help a project management professional in a industry. Is it really required? Can't a project management professional survive just with management techniques in a technical project? Saving Changes...
This is a very good question and observation. Sometimes it becomes necessary to have knowledge about technology and domain to validate certain assumptions. If you are leading a Technical project, you may not need to understand the in and out of that technology but you must be able to understand the concept and expectations.
Another classic example will be validating the estimates. How will you be able to validate the technical estimates. You must be aware at high level to understand the estimates. Technical knowledge also helps while negotiating with customer to negotiate certain requirements.
Saving Changes...
James PorterSr. Project Planner| Hitachi Rail STS USAGlenshaw, Pa, United States
I believe a PM needs to have at least a basic level of understanding of the technology involved in a project. In order to communicate to stakeholders effectively, the PM must correctly use the right terminology. There are even times when the terms used by the internal team differ from what the customer uses and the PM must not be confused by that. It's also valuable for a PM to have a grasp on what type of impact a particular issue may have.
No need to be an expert, but without any understanding at all I do not believe the PM can effectively communicate to all stakeholders. And for many projects, with a motivated PM, I think this can be done in the early stages of the project while ramping up the project with the help of the key technical people on the team. Saving Changes...
arlene trimbleAssistant IT Director| Local GovernmentAlamo, Ca, United States
Yes. I agree.
As a PM, it is helpful if you have a broad understanding of the business and the technical world to be effective. The key is you need to be able to communicate well to bridge the business and technical world by translating or transferring the information correctly. It helps if you have background info and if you are not afraid to ask questions as well to clarify the information. It helps also if you employ pairing to get estimates to minimize frictions. As a PM, it is your role to encourage a collaborative and supportive atmosphere. Saving Changes...
Without technical know-how todays project manager cannot exist solely on management skills. Even PMI CEO has also clearly made it a policy to make technical knowledge as one of the project management competence. Saving Changes...
Dominic LawProduct Manager| PCCW GlobalHappy Valley, Hong Kong
One cannot be an expert in all areas. But I see it is important to have a reasonably good understanding of the technology (assuming you are talking about a technical project) in order to communicate to each other. Otherwise the PM could be totally lost in communications with his team members. Saving Changes...
Ganesh SrinivasanGanesh PMO (PMP, PMI-SP, ITIL-F)| MNC BankChennai, India
Hi Prem Kumar,
Greetings !
Thanks for post ! In Today's changing world, Technology a must for PM and I will say adding on to Technology, Domain knowledge and Product Knowlege also must for him/her for better Planning / Monitoring and Controlling the project.
For Example : Banking Domain (in that specilasation is must, example Payments, Lending, Cards, Order mangment etc).
Products : AAA, Olympic, Finacle,Optima3,T24.
Wishing you all the best !
Thanks.
Ganehs Saving Changes...
Narender SharmaPM| Glomark Software Services Pvt LtdHyderabad, Telengana, India
I had done couple of projects and in my opinion, Technical knowledge (Domain Expertise) is essential to steer the project in right direction, I worked with PM''s without technical knowledge, They direct the team and engage in stakeholder management, most of the time goes in communication and they have to depend on SME''s for technical solutions.
Merely a project manager cannot depend on his management techniques, he should have a fair Technical knowledge of the project and the product. Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
I am going to go against the grain, Prem, and say that you can be a non-technical project manager if you have a product manager part of your team.
I worked successfully on a couple of projects where my role was strictly managerial and the product manager was responsible for product requirements. The beauty of having two individuals in each role is that it allows for healthy conflict.
The reality is you won''t have a product manager on your project and the role will have to be assumed by yourself. That means you will need some industry knowledge. Saving Changes...
Bala S DuvvuriProject Manager| ShellBangalore, Karnataka, India
In my opinion PM can use his/her technical expertise as EXPERT POWER to get cooperation from team and stakeholders so it is definitely a big boost to have technical knowledge. Saving Changes...
Gopal SahaiCorporate Trainer| Self employedNew Delhi, Delhi, India
I would read Technical knowledge as Domain knowledge. I agree with Bala Duvvuri w.r.t the point related to Expert Power. But when Prem talks of ''survival'', the entire stand point changes. PM to survive may not require Domain expertise. For that one is required to have management skills. But to excel and ensure delivery, I may agree (to some extent only) that domain knowledge will help.
In small/mid companies/projects, some dual role play is important to keep better control on project activities, progress and costs. However, while a PM may wear two caps - of managing the project and of being an expert (..ok..knowledgeable) on a subject - this may often lead to confusions and clash of priorities. To avoid the same, a detailed RACI will help. More often than not, I have experienced in smaller projects, that RACI is not formally defined and known to the team. And the subsequent confusions are inevitable.
When asked if PM Domain is a pre-requisite, I would differ on the point. However, having both expertise in one resource may add value. Saving Changes...
