Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
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

Driving clarity in risk assessment

During the introduction to driving clarity in Chapter 4, 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 early on in the project. 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!

Regardless of when the process starts, the steps are the same. Part of the process was outlined in Figure 4.3 in Chapter 4, but the full process has two additional steps that Figure 6.1 outlines:

Figure 6.1 – Risk assessment process

Figure 6.1...

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
Banner background image