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
Engineering Manager's Handbook

You're reading from   Engineering Manager's Handbook An insider's guide to managing software development and engineering teams

Arrow left icon
Product type Paperback
Published in Sep 2023
Publisher Packt
ISBN-13 9781803235356
Length 278 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
Morgan Evans Morgan Evans
Author Profile Icon Morgan Evans
Morgan Evans
Arrow right icon
View More author details
Toc

Table of Contents (24) Chapters Close

Preface 1. Part 1: The Case for Engineering Management FREE CHAPTER
2. Chapter 1: An Introduction to Engineering Management 3. Chapter 2: Engineering Leadership Styles 4. Chapter 3: Common Failure Modes for New Engineering Managers 5. Part 2: Engineering
6. Chapter 4: Leading Architecture 7. Chapter 5: Project Planning and Delivery 8. Chapter 6: Supporting Production Systems 9. Part 3: Managing
10. Chapter 7: Working Cross-Functionally 11. Chapter 8: Communicating with Authority 12. Chapter 9: Assessing and Improving Team Performance 13. Chapter 10: Fostering Accountability 14. Chapter 11: Managing Risk 15. Part 4: Transitioning
16. Chapter 12: Resilient Leadership 17. Chapter 13: Scaling Your Team 18. Chapter 14: Changing Priorities, Company Pivots, and Reorgs 19. Part 5: Long-Term Strategies
20. Chapter 15: Retaining Talent 21. Chapter 16: Team Design and More 22. Index 23. Other Books You May Enjoy

Why do we need project planning?

If our goal as engineering managers is to deliver working software, not plans, we may question why we should bother with plans at all. Fundamentally, the purpose of planning is to reduce risk during project delivery. Without plans, we face significant risks of misalignment, miscommunication, and rework. Plans help us to avoid situations where team members have differing understandings of goals, constraints, and expectations. They help us to avoid wasted effort from misunderstanding what to deliver in what sequence.

Plans allow us to think through objectives beforehand in the hope of being prepared for delivery. Plans are useful when they preempt conflict, direct efforts in harmony, and align expectations. Plans are not useful when they waste valuable build time or provide a false sense of security, for example, by missing unknown unknowns.

Given the understanding that plans have useful features but are not foolproof, we can judge that they are...

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