Which management book would you recommend to read for a fresh Team Leader?
closed as off topic by user8 Nov 22 '11 at 17:28
Questions on Software Engineering Stack Exchange are expected to relate to software engineering within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here. If this question can be reworded to fit the rules in the help center, please edit the question.
locked by World Engineer♦ Jun 26 '13 at 22:29
This question exists because it has historical significance, but it is not considered a good, on-topic question for this site, so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. More info: help center.
Peopleware: Productive Projects and Teams comes to mind.
The first chapter of the book claims,
“The major problems of our work are not so much technological as sociological in nature”.
The book approaches sociological or ‘political’ problems such as team ‘jelling’, quiet in the work environment, and the high cost of turnover.
Rapid Development by Steve McConnell.
The reason I go for this over PeopleWare is that there are a few more things in here you might actually be able to implement as a team leader. When you're a team leader (with the lack of clout that normally comes with) much of PeopleWare is largely aspirational as you're not going to be able to significantly influence working environment, salaries and recruitment and so on.
I guess it depends on whether you're looking for something on development process or on management and leadership though. While I've not read it I like the look of The First 90 Days which someone has recommended. Alternatively I quite like The One Minute Manager though plenty have issues with it (largely that it's told as a story and that it's content is obvious - which I agree with but we frequently miss the obvious so reminding ourselves from time to time is no bad thing and whatever you think of it it is at least very short).
The Mythical Man Month by Fred Brooks has a lot of great what-not-to-dos. That and Peopleware are the two that define software project management.
Read "The first 90 days..".. This book is indespensable..
If you're a new Software Team Leader, I'd recommend:
It is written from the perspective of "I've just been made a team leader - now what?" and has lots of practical scenarios presented in a clear manner. It also has good references within each section so it is useful as an ongoing reference book.
AntiPatterns in Project Management is a wonderful list of ways to do things wrong. It's a great list of things to avoid.
Well, the good ones listed are already pretty popular with most programmers. How about this one: The No Asshole Rule by Bob Sutton.
I would actually argue for Software Estimation: Demystifying the Black Art or something along those lines. Your management style, while it can be adjusted, is largely set by this time. You can always learn to do things better, faster but your style is really who you are.
Some people are opinionated jerks, others like to scream and yell while other listen and build consensus. If you have been developing for any length of time those personality traits are either pretty much set or fairly visible. You new position is going to require a lot of scheduling: your time and other people's time. To succeed you better get it right (or mostly right).
Your status as a freshly minted Team Leader will be determined by your ability to deliver projects on time.
Your own. Train your leader by a series of discussions and mentoring sessions, and have your trainee keep a private journal of situations, responses, and successes or failures. Essentially, they will write their own book. This exercise is not so much for the book itself or reference- it is to encourage the act of reflection.
Then, after the freshly-minted leader has a grasp of the issues, select some of the great books posted in other posts.
My point is that you should have some experience with leadership and management before you go reading books about them, simply because you won't know enough about the subject matter to really understand, appreciate, and relate to what you've read. For example, you wouldn't advise someone to read Code Complete before they wrote their first line of code, would you? The same applies here. Get your feet wet so you have something to relate to, and then go for the books.