WEBVTT 00:02.240 --> 00:05.560 What are the common responsibilities for 00:06.060 --> 00:10.240 a tech lead? As I mentioned before, it's not a standardized role 00:10.740 --> 00:14.800 as it is the Scrum master. So it is defined 00:14.960 --> 00:18.480 differently among companies. There is though 00:18.980 --> 00:22.760 a common ground and there are common responsibilities and we 00:23.260 --> 00:26.570 are going to look at those in this video. Before that, 00:26.810 --> 00:30.370 there is something that I want you to be aware of is 00:30.870 --> 00:34.930 that the tech lead is an important role and you 00:35.430 --> 00:40.810 are in the middle. It's a collaborative role and 00:40.890 --> 00:44.970 you are in the middle. And no matter how the 00:45.050 --> 00:47.610 company is organized, no matter the department, 00:48.250 --> 00:50.330 definitely you are going to be in the middle. 00:51.460 --> 00:57.220 As you can see, you're in the middle. And these are the different possible categories 00:58.100 --> 01:00.980 of colleagues to interact with. 01:01.940 --> 01:05.140 So you interact with your 01:05.640 --> 01:09.220 team, the dev team, the other engineers, 01:09.700 --> 01:13.380 and then are the business analysts and the product owner. 01:13.700 --> 01:17.140 It can be a product team. If you work on a product, 01:18.040 --> 01:21.880 then there is the QA team, there is the architect, 01:23.320 --> 01:28.760 there is the project manager, if there is one for the project and 01:29.260 --> 01:32.640 you can even interact with the client. Now going 01:33.140 --> 01:35.320 back to the common responsibilities, 01:37.080 --> 01:40.920 we are going to look at those. I'm going to share the 01:41.000 --> 01:42.120 screen again. 01:44.690 --> 01:48.290 So this is what I came up with in regards to 01:48.530 --> 01:52.610 what are the common responsibilities and some of them, 01:53.110 --> 01:56.530 it might be that they do not apply to you or 01:57.030 --> 02:00.850 it's not something that is requested in your company and 02:01.350 --> 02:04.650 it's something that might be useful for you in the future when 02:05.150 --> 02:08.570 you will work in a different company or just for 02:09.070 --> 02:13.150 you to know like this is what is usually needed. 02:13.390 --> 02:16.750 Okay, so the first one is I will 02:17.250 --> 02:22.350 start with the mentoring. So it is expected of you to mentor 02:22.850 --> 02:26.830 people. And when I say mentor, I mean you 02:27.330 --> 02:30.430 are a senior engineer, you have experience 02:31.550 --> 02:36.120 and you can influence and you 02:36.620 --> 02:40.920 can influence and contribute to the growth of your colleagues, 02:41.240 --> 02:44.960 colleagues, engineers through different ways. It can 02:45.460 --> 02:49.320 be through code review, it can be through pair programming, 02:50.200 --> 02:54.360 it can be a conversation around the business of 02:54.860 --> 02:58.600 the application you are working on or product 02:59.100 --> 03:02.600 that you are working on to clear some business aspects as you 03:03.100 --> 03:07.540 know more. It can be you hand over one of the topics and 03:08.040 --> 03:12.380 it can be you even do workshops around a 03:12.880 --> 03:16.260 framework that you use or a new technology or something that you 03:16.760 --> 03:20.660 see missing for all of them. You can create a workshop and 03:20.900 --> 03:24.620 do that. So this is the mentoring part you understand, for their 03:25.120 --> 03:29.060 growth. The second one that I put here is making technical 03:29.220 --> 03:32.670 and and non technical decisions. What do 03:33.170 --> 03:36.430 I mean by that? Is for example, 03:36.930 --> 03:40.190 for the technical ones, it might be that you work with an architect and 03:40.690 --> 03:44.230 you decide together what frameworks to be used. If it Starts now. 03:44.790 --> 03:48.830 The software that you are working on or a 03:49.330 --> 03:53.710 new feature is being developed and you 03:54.210 --> 03:57.430 can come up with, okay, let's use this new framework. It will 03:57.930 --> 04:02.710 help us with the performance and with the implementing 04:03.210 --> 04:06.990 it faster. And this you can, as I said, you can work with an architect 04:07.490 --> 04:10.390 or you can do it on your own. It depends. It's up to you. 04:10.890 --> 04:14.510 And then the non technical decisions, it can be 04:16.110 --> 04:19.950 we will release in that date or we 04:20.450 --> 04:23.080 will organize yourself this way. 04:23.720 --> 04:25.640 These are the non technical decisions. 04:26.280 --> 04:30.640 Okay, the next part is communicate the technical and 04:31.140 --> 04:34.600 non technical decisions. So it's to 04:34.680 --> 04:38.320 ask yourself who needs to be 04:38.820 --> 04:42.320 informed, who needs to know that it might be at the beginning 04:42.820 --> 04:46.080 that you don't know or maybe you work in a company 04:46.580 --> 04:50.120 in which the processes are clear and you know who needs to be informed. 04:51.080 --> 04:54.720 If not, you can think about, okay, who needs to 04:55.220 --> 04:59.920 know that we are going to use this framework to implement this 05:00.420 --> 05:03.960 new feature. And once 05:04.460 --> 05:08.000 you have that answer, you can. It's for you to communicate the 05:08.500 --> 05:11.920 non technical decisions. Okay, we are not going to release in that 05:12.420 --> 05:16.690 date, we are going to release a week later. Who needs to be informed? 05:16.770 --> 05:20.050 Probably everybody. Yes. So this is. 05:21.010 --> 05:24.570 It's part of your responsibility to 05:25.070 --> 05:28.530 communicate all the decisions that happen inside the team 05:28.690 --> 05:31.890 and it's something communication. We are going to look in the next weeks. 05:33.570 --> 05:36.530 The next one here is unblock the team. 05:38.050 --> 05:41.730 Unblock the team is you're the, as I said, you're in the middle. 05:42.610 --> 05:46.970 If something happens and the 05:47.470 --> 05:51.090 team cannot work, it's a priority for 05:51.590 --> 05:55.930 you to unblock that. It can be that the 05:56.430 --> 05:59.290 connection to a server is not possible. Okay, who do you need to talk? 05:59.790 --> 06:02.450 What do you need to do to make it happen? To shorten the time. 06:02.850 --> 06:06.410 Then it can be that user 06:06.910 --> 06:10.700 story doesn't have enough details or something is happening and somebody is 06:10.860 --> 06:13.740 blocked by that. So you go, okay, 06:14.060 --> 06:18.780 who do I need to speak with? What do you need? So you make 06:19.280 --> 06:21.100 things move and unblock them. 06:22.460 --> 06:27.220 A big part of the role is that. And the 06:27.720 --> 06:30.060 last one that I put here is backlog refinement. 06:31.420 --> 06:35.100 If you don't work in a Scrum environment, I mean 06:35.600 --> 06:39.180 the planning and prioritizing the tasks. 06:40.460 --> 06:45.260 And when I say backlog refinement means that you work with closely 06:45.760 --> 06:50.500 with the product owner and you 06:51.000 --> 06:54.420 refine like you prioritize the user stories. So it works also 06:54.920 --> 06:58.980 for the engineering team or it can be that 06:59.480 --> 07:02.540 you refine the user stories to be more clear or request 07:03.040 --> 07:06.580 from others to add more details. So you are involved 07:07.080 --> 07:10.860 in this process as part of leading the development 07:11.100 --> 07:13.100 team. Okay. 07:14.780 --> 07:18.500 Now, if you do work in a 07:19.000 --> 07:23.180 Scrum environment, you will find a link with an article to 07:23.680 --> 07:28.180 see what is the role of a tech lead inside of a 07:28.680 --> 07:32.390 Scrum team. So you get clarity of what can be expected of you. 07:33.430 --> 07:36.870 Now that you know this, you can think about. Okay, 07:39.030 --> 07:42.790 this is. What is. This is actually that I'm already doing. 07:42.950 --> 07:46.150 This is what I would want to start doing. 07:46.710 --> 07:50.230 And you will build on the assignment for this week. 07:50.790 --> 07:53.590 Okay, thank you. See you soon.