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 Empowering managers to efficiently manage technical projects and build a successful career path

Arrow left icon
Product type Paperback
Published in Dec 2022
Publisher Packt
ISBN-13 9781804613559
Length 214 pages
Edition 1st 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 (19) Chapters Close

Preface 1. Part 1: What is a Technical Program Manager?
2. Chapter 1: Fundamentals of a Technical Program Manager FREE CHAPTER 3. Chapter 2: Pillars of a Technical Program Manager 4. Part 2: Fundamentals of Program Management
5. Chapter 3: Introduction to Program Management 6. Chapter 4: Driving Toward Clarity 7. Chapter 5: Plan Management 8. Chapter 6: Risk Management 9. Chapter 7: Stakeholder Management 10. Chapter 8: Managing a Program 11. Chapter 9: Career Paths 12. Part 3: Technical Toolset
13. Chapter 10: The Technical Toolset 14. Chapter 11: Code Development Expectations 15. Chapter 12: System Design and Architecture Landscape 16. Chapter 13: Enhancing Management Using Your Technical Toolset 17. Index 18. Other Books You May Enjoy

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...

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