Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
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 from requirements to planned work

In Chapter 5, we discussed the importance of driving clarity in all aspects of a project or program. Out of all of the areas where driving clarity is needed, plan management is the most important.

When writing a project plan, we might find ourselves asking why we are doing it. ā€œWhy are we doing this?ā€ I ask myself every time Iā€™m writing one, even though it is one of the aspects of project management I enjoy the most. The answer to why we do it is simple: it enables us to be a force multiplier. We know the work that needs to be done and so does everyone else. The team spends less time on determining what and when and instead focuses on how to achieve the tasks and goals. Driving clarity in requirements early on takes less time than correcting the issue later in execution as this can lead to bad estimations due to poor understanding, which results in longer timelines.

The first step in driving clarity in...

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