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

Resolving conflicts

Conflict resolution is one of the key methods by which we find a path forward as many issues are rooted in disagreement or misunderstanding between multiple parties. As such, any place where a TPM can run into an issue, conflict resolution can make an appearance.

Planning

Conflicts during the planning phase usually occur while analyzing requirements but can also occur while creating the project plan. We’ll go through a few examples and see how your technical background can help resolve these conflicts.

During requirement analysis, disagreement on a requirement or an ambiguous requirement is common. As you work with your stakeholders, any clarification may introduce new complexities or insights and can steer the conversation organically. I have found that knowing my system behaviors and complexities helps during these conversations.

For instance, a recent project had a requirement to take a regional functionality and make it available globally...

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