Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Technical Program Manager's Handbook
  • Table Of Contents Toc
  • Feedback & Rating feedback
Technical Program Manager's Handbook

Technical Program Manager's Handbook

By : Joshua Alan Teter
5 (3)
close
close
Technical Program Manager's Handbook

Technical Program Manager's Handbook

5 (3)
By: Joshua Alan Teter

Overview of this book

The role of the Technical Program Manager (TPM) is crucial in the tech industry, bridging the gap between technical expertise and business acumen. The second edition of the Technical Program Manager’s Handbook offers a comprehensive guide to excelling in this role. Building on the foundational concepts from the first edition, this updated version introduces new chapters that explore the integration of AI and Emotional Intelligence (EI) in program management. These crucial additions complement the broader focus of the book on bridging business and technology but don’t overshadow it. You'll learn how to apply AI-driven tools to enhance project planning, risk management, and stakeholder communication, as well as how to leverage EI to build strong team relationships and improve leadership effectiveness. This book provides practical tools, methodologies, and case studies, offering insights from industry leaders to help both aspiring and practicing TPMs apply advanced concepts and strategies effectively. It also explores the unique aspects of the TPM role in major tech companies, helping you to navigate and thrive in your career. By the end of this book, you'll have a clear understanding of the TPM role, along with a breakdown of the necessary technical and program management skills, to develop a clear roadmap for your career.
Table of Contents (21 chapters)
close
close
Free Chapter
1
Section 1: What Is a Technical Program Manager?
5
Section 2: Fundamentals of Program Management
13
Section 3: Technical Toolset
19
Other Books You May Enjoy
20
Index

Deciding when to build a program

Now we know what a program and project are, but the discussion has involved defining the boundary using a pre-existing program as an example. As a TPM, one of your jobs will be deciding when a program needs to be created and whether it is appropriate to the needs of your organization to do so.

From a project perspective, knowing when to create one is straightforward – you receive requirements to deliver a new application or service, a new feature, and so on, and you create a project to deliver on those requirements. Projects can be done standalone and do not need to be part of a larger program. In many industries, this is how almost all work is done: through independent and discrete projects.

However, knowing when a program should exist is a bit more nuanced and depends on the situation. There are two avenues through which a program is created: from the beginning when requirements are determined and during project executions where a...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY