Managing the Unmanageable: Rules, Tools, and Insights for Managing Software People and Teams by Mickey W. Mantle
My rating: 5 of 5 stars
If you are new to managing a team this is a must read for you. While the book is intended for managers of programmers (developers, software engineers, etc…) I believe this book applies to just about any sort of creative. Obviously, some sections will be less applicable to architects like the agile sections, but in general, creatives are creatives. The authors, to some extent, recognize this by continually comparing software developers to musicians. Arguing, in fact, that the best programmers are typically fantastic musicians. There’s a similarity in the way the brain works between musicians and developers. I think this applies to other artists as well, especially ones that under went rigorous training to be an artist. There are processes you need to follow to enact your vision.
Anyway, the book itself offers very candid advice on everything hiring, firing, building local and remote teams, coaching, rewarding, and having fun.
The authors argue that hiring is the most important job of any manager. I think this is true from my experience interviewing people and managing people. Whenever you hire someone the work environment shifts. So you need to make sure that whatever change the person brings is a net positive for the team. To ensure that you get the right combination of fit and skill you must have a rigorous process for finding potential candidates, screening candidates, and interviewing candidates. If you do not you will pay for it later by losing your best people or being required to fire that hire in the future for lack of performance.
All this and templates are laid out in the book. The tools and rules of thumb are fantastic for first time managers and managers that have struggled to hire the right team.
The authors argue the most important functions of a manager are Hiring/Firing, Coaching, Developing individuals and teams. I think this is right. The manager should be technical enough to help with the team as needed, but shouldn’t be expected to roll up their sleeves too much. Their skill is more important in investigating logical approaches than the specifics of coding. However, there are a lot of people that believe their manager should be able to do their job. Which i think has a lot of merit.
This book also has some great ideas of how to convert traditional managers into agile managers. Ironically, if you follow their advice through most of the book, you’ll be well positioned to be an excelled agile manager positions to remove impediments.
I highly recommend this book for any one managing programmers, engineers, or creatives in general.