Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Technical Program Manager's Handbook

You're reading from   Technical Program Manager's Handbook Unlock your TPM potential by leading technical projects successfully and elevating your career path

Arrow left icon
Product type Paperback
Published in Sep 2024
Publisher Packt
ISBN-13 9781836200475
Length 368 pages
Edition 2nd Edition
Arrow right icon
Author (1):
Arrow left icon
Joshua Alan Teter Joshua Alan Teter
Author Profile Icon Joshua Alan Teter
Joshua Alan Teter
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

Preface 1. Section 1: What Is a Technical Program Manager? FREE CHAPTER
2. Fundamentals of a Technical Program Manager 3. Pillars of a Technical Program Manager 4. Career Paths 5. Section 2: Fundamentals of Program Management
6. An Introduction to Program Management Using a Case Study 7. Driving Toward Clarity 8. Plan Management 9. Risk Management 10. Stakeholder Management 11. Managing a Program 12. Emotional Intelligence in Technical Program Management 13. Section 3: Technical Toolset
14. The Technical Toolset 15. Code Development Expectations 16. System Design and Architecture Landscape 17. Harnessing the Power of Artificial Intelligence in Technical Program Management 18. Enhancing Management Using Your Technical Toolset 19. Other Books You May Enjoy
20. Index

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 a program, you need to refine the goals in the same way you refine the project requirements. In Chapter 4, we stated that the Mercury program’s goal is to have a P2P messaging application with a 100% user reach. This is an okay goal with enough wiggle room to achieve success, but from a requirement standpoint, it’s too vague. What is user reach? How do we measure 100% of that?

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

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime