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

Driving clarity in risk assessment

During the introduction to driving clarity in Chapter 5, we discussed the cyclical relationship between project planning and risk assessment. Now, we’ll drive clarity in terms of what risk assessment is and how we continue to manage risk throughout the project’s life cycle.

Risk assessment starts as soon as you have enough information to start assessing, which can be as early in the project as initiation. If you start with a project in a domain that you know very well, a single paragraph about the goal of the project may be enough to start analyzing risks. In other cases, where the domain or project itself is too vague, it may take a full requirements document to start analyzing, which is in itself a risk!

I’ve been in the same domain area for over a decade, so I know the business aspects of the tax domain very well. I also know our technical landscape and product vision. As such, when new legislation is passed, the legislation...

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 $19.99/month. Cancel anytime