This book aims to provide help and advice for IT professionals in this situation by offering solutions to the most commonly encountered problems, such as getting a project out on time, coping with the demands of leading a team, implementing new methodologies or technologies. It is written by a team leader for other team leaders with a focus on practical advice rather than management theory or process issues. It would be targeted at experienced software engineers, developers and architects who have been promoted to the role of team leader.
I got this book because I had recently been promoted and wanted to get a better handle on how to be a technical leader. This book isn't really about that; it's more about how to be a project manager or a team lead. And the problem is that it describes how to work inside the (in my opinion, rather outdated) waterfall software development model. I am a believer in Agile (not a zealot; there are Agile tenants I don't consider important or useful), so some of the basic assumptions about how work is conducted struck me as outdated and inapplicable.
Whitehead's attitude is at times very flip, which undermines the professionalism he advocates throughout the rest of the text.
If you are just getting started in the working world, this book might give you some insight as to how to conduct yourself, especially as you move up the corporate ladder. But if you've been in the business for even more than just a few years, most of what it says is just common sense.