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
Technical Program Manager's Handbook

Technical Program Manager's Handbook

By : Joshua Alan Teter
4.3 (15)
close
close
Technical Program Manager's Handbook

Technical Program Manager's Handbook

4.3 (15)
By: Joshua Alan Teter

Overview of this book

The technical program manager (TPM) is a relatively new role born out of the need of the tech industry to have a specialized practitioner who speaks both tech and business and leverages this bilingual talent to get results that no one else can. This book dives into what makes a TPM tick. You’ll find out which project and program management skills will help you shine and how you can apply your technical skills for effective results. This book looks at the TPM role across the Big Five tech companies (Amazon, Google, Microsoft, Apple, and Meta) to help you discern the most effective skills to be successful no matter which company you work for. Are you already a well-performing TPM looking to see what’s next? This book identifies the career paths for a TPM at the Big Five to help you decide the next step for you. By the end of this book, you’ll have a clear understanding of how to be a TPM, along with a breakdown of the necessary technical and program management skills to develop a clear roadmap for your career.
Table of Contents (19 chapters)
close
close
1
Part 1: What is a Technical Program Manager?
4
Part 2: Fundamentals of Program Management
12
Part 3: Technical Toolset

Exploring the differences between a project and a program

Many of the tools and processes are the same between a project and a program. One major difference is scope. In this case, there is the program scope, which has its own set of requirements in the form of the program goals. These requirements are relayed down to the projects that impact them. Though I’ve been referencing the Windows Rollout Project, these requirements could easily have been for any of the other platforms.

When starting the program, you need to refine the goals in the same way you refine the project requirements. In Chapter 3, we stated the Mercury program’s goal is to have a P2P messaging application with a 90% user reach. This is an okay goal with enough wiggle room to assume success, but from a requirement standpoint, it’s too vague. What is user reach? How do we measure 90% of that?

There are also technical issues with this statement. Let’s say that the user base means all...

Visually different images
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Technical Program Manager's Handbook
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

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

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon