Our organization is undertaking a re-org to solve our current resource and communications issues. I know, a re-org never solves anything, etc. With that being said, I was tapped to go from an individual contributor (aka tech lead/architect) to leading a team of maintenance developers and analysts.
I'm very aware of all of the stigmas associated with this kind of move: PHB, those that can, do - those that can't, get promoted, just because you are a good coder won't make you a good leader/manager, etc. So I am a little paranoid about making mis-steps.
As a tech lead, I'd like to think that I was conscious of the trends in the industry and took steps to educate myself. I've read all of the main books that are typically mentioned: Peopleware, Mythical Man-month, Code Complete, Pragmatic Programmer, etc.
As I am entering this new phase, I'm feeling a little underprepared and am looking for the equivalent must-read teamlead books. Of course, keep in mind that this is for a maintenance team in a big bureaucratic organization, so my ability to make sweeping changes (ala Peopleware) are a little limited.
What do you recommend?
p.s. I know that this is a little off-topic for the site (not directly programming related and doesn't have a concise answer) but I've seen other threads that are just as OT and, more importantly, I've been impressed with the responsiveness of the community so far.
Thanks, Matt