What books would you recommend for the future Team Lead?

Question

Project management

Good afternoon,
I have been working in IT for quite a long time (6-7 years), now I hold the role of Senior Software Developer and plan to develop towards Tech/Team Lead. Please recommend books that will help you gain the skills and knowledge needed for this role.
Thanks in advance!

Answer 1

Everything with the prefix Lead is no longer about technology, but about people. Read everything you can find about Soft Skills and basic psychology.
If you want to go straight in a serious way, then the Stratoplan courses, they just have a set for the fall.

Answer 2

I'll attach screenshots, too lazy to type (((
And I also recommend the book by J. Rainwater: How to Graze Cats
Maybe something is a little outdated, but overall excellent material.

Answer 3

I will say from the bell tower of my poor experience as a team leader: the main thing here is to keep a balance between being an asshole or being a rag. And to be able to push through your productive asshole with the softness of a rag. And then it will turn out to be more profitable to be an asshole - because no one scatters anywhere, but only dream about it for years, and you tear their skins off. And you get paid more by another asshole, one floor up, who doesn't even ask such questions.
Offtopic, not related to the field and IT: in my experience in a bunch of different fields, this one, on the floor above, is usually one of two: a lucky criminal from the 90s, who climbed there on corpses and forged documents. He may be rehabilitated (that's good, there is something to work on) or not, but old and slightly limp - but still bad. Or the cub of this criminal: and he / she can be a relatively sane person, but not without surprises. All of them, as a rule, absolutely do not rummage in their field, and everything rests on a pair of team leads (or whatever they are called) - old-timers. Whoever is an asshole is more likely to become one of them.
Sorry for being off topic.

Answer 4

these skills come with experience, you need to have a broad view of technology (6-7 years is very little for a team leader) You
have to work a lot with people, it is important to have a sincere desire to help, openness, in cases of conflict, be able to smooth them out, not be toxic, not categorical, tactful, be able to motivate and not demotivate - otherwise the team will scatter. Timlid is authority (and authority must be earned, not read)

Answer 5

1. Scrum management - sprints, distribution of tasks, planning, etc.
2. Conflictology.

Answer 6

Drink with demobilizations for a couple of days - they will teach you how and what.

Answer 7

Psychology, lots of psychology.

Answer 8

Read this article (almost the size of a book, as requested), you will find a lot of useful information about everything that awaits you on the path of product development and work on software - https://vc.ru/flood/71014-v-budushchee-deystviteln. ..

Answer 9

You don’t need to develop towards the team lead - this is an intermediate state of a specialist who has not yet decided - and not a programmer (often programming is no longer a desire and programming skills begin to be lost), and not a manager (does not have time to master the necessary knowledge of management), just while he thinks where to develop further , either continue to program, design software and develop as a strong technical specialist (IT architecture), or go deeper and move into professional development management and become a scrum master. Professions of the future .

Answer 10

Try not to miss the basics of management. Surprisingly, 90% of "specialists" neglect the basics of their profession. Then they complain. They complain a lot.