September 28 & 29, 2020 | Virtual
Please login or join to subscribe to this thread
I think TPM means you may have to be part of the technical project team and take some technical tasks along with your project manager role.
Technical project managers act as an SME as well as they manage projects too if projects demands, they can be techno-commercial and they have a knowledge of technology as well as technical skill and project management. they are more expert in technical skill compare to PMs skill, Technical project managers has more weight than Just PMs, Also had more respect from internal teams and no one challenge/fool them easily.
PMs that don't have technical background act more like facilitators than real decision makers. Some of them claim that technical background is not needed to successfully manage a project but in reality these PMs don't take too many decisions, that's why they can "manage" the project.
A senior technical expert for example may decide to do a very high standard work that would take a long time to complete when a work with a lower standard but still high would be enough to complete the work faster and achieve the required quality. A non-technical PM can't direct the expert on how to do the work and as such he can't ensure the team finishes the work on time.
Typically when an organization seeks a technical project manager is looking to fill two roles in one person, thus someone who can lead a project and also carry out hands on some of the project activities, as an SME. This is a practice that should be avoided by all the reasons already exposed by peers in previous postings.
Thank you for all your thoughts.
By reading the ideas shared, It is apparent that the two are different roles.
I am clear with the Project manager role, as that is what I do. I am a technical person too but I never called myself as a technical project manager as I manage diverse and hybrid projects and programs ranging from process improvements to technology implementations and transformations in the financial, healthcare and workforce management industries. Projects are unique and they vary a lot. I am not an expert of all technologies and I cannot limit what I do to what technologies I know and that is the beauty of project management. Projects may include many things and are not limited to technology related executions. Project managers should be able to manage any project their companies decide to undertake. A part of managing a project is defining human resource requirements which may include the identification/engagement of SME's already working for the company or the hiring of SME's. Project management is a transferable skill. But of course, experience and related skill sets are best in considering for a PM from a pool of PM's. But if you already have a PM and you want to initiate a project that is unfortunately something new for your existing PM, would you get a new PM with the matching technology savviness or would it make more sense to look for SME's to work with the PM?
Thanks a lot. :)
This is crucial otherwise the PM can't direct the team members, can't check and review the work being done and in the end he can't ensure the work is delivered on time.
When it comes to managing the team a non-technical PM is just a tracker and a messenger and not a real manager or leader for the team. This is not theory is something that I have noticed.
As a systems engineer I was asked to lead a datacenter migration project in 1987. I was lucky and successful, building strong on communications. After that I decided to switch my profession to project management, dealing with people and less technology. I cut all ties to technology and focused on my target, bringing in technical SMEs even if I could have done it myself (I thought). Four eyes see more than two and when the going gets tough it is good to have someone cover your back.
Please login or join to reply