A person –
1. Expert in different development methodologies
2. Possess strong technical concepts and designing techniques
3. Has problem solving skills and capable to learn new technologies
4. Is innovative in thinking and go-getter in arriving at a solution to resolve complex business problems
5. Is skilled in troubleshooting, software development processes and ability to understand and implement client requirements
6. Communicates effectively with teams (both internal and external)
7. Shows good time management and multitasking capabilities
8. Effectively lead teams and inspire others to achieve goals through innovation, quality and excellence
9. Identifies strengths and weaknesses of team members and suitably make changes if required
10. Capable to handle complex / sensitive issues
11. Encourages team interaction, boost employee motivation and appreciate team contribution
12. Introduces best practices into the team
13. Provides direction and technical expertise to team members in design, development, roll out of the product and support
14. Takes ownership of the deliverables and manages stake holders
15. Identifies resource requirements, do capacity planning and manage software and hardware availability
16. Provides technical training to teams when required and serve as a technical mentor to team members
17. Identifies technical debts and evangelize them
18. Is proactive with good analytical skills
19. Dynamically manages evolving challenges and ability to prioritize the tasks quickly based on
20. Understands work-life balance
Technical PM may not only refer to software development or other IT disciplines. It usually refers to a PM with a strong technical background (degree or the like) who is not only familiar with the industry, but also serves as a kind of "senior architect".
Product Operations Program ManagerBarcelona, Cataluña, Spain
Hi George,
Thanks for posting this interesting question. A Technical PM manages projects (adhering more or less to standardized PM methodologies) AND is also typically a Subject Matter Expert (SME) on the very same project subject. Therefore, at the end this person is developing PM functions but is also a key team member in the execution of some of the project activities.
That may raise another question: Technical PM Vs Administrative PM? Saving Changes...
Philippe SchulerSenior Instructor/Lecturer in Project/Program/Account PMO Management| Independant ConsultantLes Choux, France
I agree with Eduard. A Technical PM is first a SME. Saving Changes...
Avinash KharePM II| MAP-IT Consultant Project ManagementAmbernath (East), Maharashtra, India
I agree with Christina.Technical Project Manager will have a JD more focused on the technical domains. Saving Changes...
Stanly JohnsonSenior Reliability Engineer| Maaden Aluminium CoMumbai, Maharashtra, India
Hi George,
There are many types of projects, based on the initiative a financial, social, civil engineering, IT, Engineering, procurement and Commissioning (EPC), etc. In such classification, the domain knowledge of the project manager (PM), plays a major role in the success of the project. A project where technology is involved , the technical knowledge of the PM, is definitely advantageous and the stakeholders may call him PM (Technical), for that project. Saving Changes...
Rangavittal VasuprakashHead of Projects - Kingdom of Saudi Arabia| PETRONASH ARABIADubai, United Arab Emirates
I too agree with Mr. Stanley and Christina.
PM with a strong domain knowledge to a particular industry who is capable of resolving the technical issues pertaining to the Job and balances with Project Management skills to deliver the Project successfully. Saving Changes...
For a short answer I thin there are two types of Technical PM:
- The one that deals with technical issues, more of a SME but given the title so he/she is part of the Management Team
- The one that gained the position out of knowledge and that uses the Knowledge/Expert type of power to influence Saving Changes...
Community Champion
