6 Best Practices for Technical PMs
The role of a technical program manager (TPM) is complex. While the basic job description is like a project manager, a TPM requires additional technical expertise and more than a general knowledge of the issues faced by each team. A truly effective TPM takes a dynamic and holistic approach to successfully execute and deliver a program. While TPMs should not hesitate to call in experts when complex issues arise, they also should be able to understand and communicate the teams’ work and act as a liaison between teams and management. Building relationships with team members helps eliminate information silos, where members do not relate to and communicate with each other.
The role of a TPM
At the most basic level, a technical program manager’s job is to deliver and execute a program. A TPM defines and drives the program’s execution strategy, considers whether the appropriate technical decisions are being made, and partners with all teams and stakeholders involved in the development the program, including those working on software, hardware, reliability, sales, and other areas. It’s important for TPMs to understand the technical aspects of the entire program and so they can bridge the communication gap between the technical and non-technical stakeholders and teams. Ultimately, a TPM’s job is to combine the technical knowledge of the program with …
Please log in or sign up below to read the rest of the article.
|
"Work is what you do for others . . . art is what you do for yourself." - Stephen Sondheim |
