What to do when the team lead leaves the team?

Question

Career in IT

Из команды уходит тимлид, который в принципе тащил всё на своих плечах, у нас есть месяц узнать у него и вытащить из него всю информацию. Что первым делом в такой ситуации делают?
Работаем под веб и моб устройства. В основном это C#, PHP, SQL, JS и много работы с базами данных. У нас спортивная организация, много разных внутренних и внешних проектов для спортсменов и персонала. Сможет ли команда существовать без тимлида, у нас ещё руководитель ИТ отдела, он умный, но всеми задачи руководил тимлид. Вроде нашли какие проекты на каких серверах находятся, гитлаб использует, т.е. контроль версий тоже не проблема. Хотелось бы услышать что-то более в глобальном смысле.

Answer 1

Вставать на его место с кратным повышением зп, это же очевидно.

Answer 2

Обновляют резюме.
А если серьёзно - какой ответ вы ожидаете? Не указан ни стек технологий, ни тип проекта...
Проекты, автобусное число которых равняется единице, обречены на провал.

Answer 3

Demobilization is inevitable! Give him an album to remember!

Answer 4

The answer is obvious - hire a new team lead, because. There are no irreplaceable people, there are interchangeable people.
Most likely, there will be a drawdown in terms of the timing and quality of task execution in the region of 3-6 months, depending on the current volume of the code base.
You also need to go a little from the other side. Ask yourself the question: "Why was it the team lead who dragged everything"? Does he have no subordinate seniors / middles, or is the company unable to hire someone stronger than a junior due to financial restrictions? The main task of the team lead is to coordinate the work of the team, and not to write code / solve problems. Of course, you need to help people if they are stuck somewhere. Of course, you need to send a subordinate if he does not know in which direction to move. However, it is the subordinates of the team leader who should write the code / solve problems, and not he himself. Then, after the leader leaves the team, it moves by inertia for another 2-3 months without any external management, and this time is enough to hire another person and give him the opportunity to sort out the current affairs of the company.

Answer 5

"in principle, he dragged everything on his shoulders" - why then were you listed at work?
With such initial data, try to figure out what is as detailed as possible. Pick the most incomprehensible code, find out how and why. What else can be said. No miracle advice will be given to you here.

Answer 6

Пытаться на некоторых условиях договориться с ним о поддержке. Если это критично и возможно.

Answer 7

ну логично что втаких случаях заставляют писать документацию навсе проекты
судя по всему ее вы не вели совсем.

Answer 8

Обычно, незаменимых людей нет. Договоритесь с "бывшим" о консультациях и его условиях, возьмите контакты. А пока он еще на месте, постарайтесь получить максимум информации.
Так или иначе все проблемы, которые возникнут после его ухода, решите, а со временем все освоите сами.
Ну и в дальнейшем повышайте число автобуса (или понижайте :)

Answer 9

"can a team exist without a team leader, we also have an IT manager, he is smart, but the team leader managed all the tasks."
So let your smart IT manager ask.
PS Either the project will die, or you will find a miracle replacement, or figure out how to do things differently, but obviously it will be much worse if you already don’t know what to do without a team lead.

Answer 10

In your case, the project will have to close or start from scratch.
As I understand it, in real life, one person was involved in the project, and all the rest were nothing more than extras (this happens very often). In the end, he was tired of this situation and he decided not just to leave, but to stir up his project. In short, now you are his competitors and he will not help you.
If more than two people are involved in the project, detailed documentation must be kept. Well, of course, everyone in the group should know their part of the work.

Answer 11

If you are an intelligent specialist, the team leader will take you with him. Otherwise... you don't need to think about this problem at all.

Answer 12

do not worry, developing from scratch is always easier and more interesting
(true for the developer, for the manager - vice versa)

Answer 13

1. Quite a regular situation. Team leads, admins, managers, creatives, accountants, mechanics are leaving - and so on, who carried everything on their shoulders and knew everything ...
2. It is best to agree that he would help and bring the receiver up to date for a separate fee. Since some things may still remain unexplained 10 months later.
3. Someone needs to start taking cases as early as possible.
4. There are no irreplaceable ones. Find a qualified replacement. It will be even better than the old one.

Answer 14

The team leader closes two important areas at once at the operational level
1. Maintaining the process.
2. Problem solving and related team support. if we are talking about development, then this is broad knowledge beyond the core technology stack plus knowledge of the domain area.
With the 2nd point it is more difficult - experience is needed here. Without it, nowhere. But in my opinion it can be compensated by the team. The main thing will be to know who is covering what piece of knowledge and where the white spots are.
First point. He is very important. Without experience, the process cannot be improved. But documenting it is just a must-have. This can be done by the team leader himself, if he is good, then this should have been described long ago. It's time to bring this documentation up to date.