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
Conferences
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

Lingering questions

In this handbook, there is a broad range of information to help engineering managers do their best work, but there are a few topics not covered in previous chapters. Along with team design questions, you may have a few more lingering questions, which will be addressed here.

What are squads, chapters, guilds, and tribes?

If you have heard these terms used in the context of team design, you might have heard them in reference to the Spotify model. In the early 2010s, Spotify wrote extensively about its team design approach and popularized a structure consisting of a product aligned organization with formalized communities of practice, as shown in Figure 16.5:

Figure 16.5: The original Spotify model of team design

Figure 16.5: The original Spotify model of team design

In the Spotify model, a squad is a cross-functional team working together on a specific product area. A chapter is a small community of practice with a narrow area of focus. A guild is a large community of practice that...

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