I work as senior software engineer. I have been asked to play the team lead role in a new project which is for a short duration of 3 months. This project is similiar to another project in our organization and 2 junior developers have been pulled out from that project and will be working under me in this new project.I have been told by the onsite that since they already know this code they will be to doing the main coding in this project quickly and your role will be lesser coding and mainly to ensure that requirements are properly taken and not missed, ensuring that UI is recieved on time from the UI UX team etc. They have been told that they will be doing most of the coding and I will be helping in the functional requirements point of view more than the technical point of view.
Since this is a new role for me I have some questions which will help me do this job better:
1) I have previously been doing mostly coding , so in any daily status update and timesheet I used to say that I worked on implementation of this or that today. Now that I am expected to mostly be doing non coding tasks in this project, what can I say as the daily status and mention in timesheet. E.g I cant say that today I made sure requirements are taken correctly and not missed or today I did follow up with UI UX team to give us UI on time. So what shall I say for these non coding tasks.
2) Any other suggestion to help me do my new role better?
"Yesterday, I researched the performance requirements. Today I plan to meet with developer X to incorporate what I learned into the code."
You still report on what you do; it's just at a higher level. I also recommend talking to someone who is a lead in your current company about what is expected. Are you supposed to help with quality? Pair with the developers? etc
Thank You. Earlier during the work day my focus was only on that my work should complete and I have go give update regarding it.
Now I think during the day I should also have to keep awareness of every aspect of the project and the overall status too. I need to keep awareness of what is expected and where exactly do we stand overall.
From what I think out of this, missing the requirement would be a bigger issue than delay in work. For requirements, I take fast rough notes from the daily meetings in a notepad/copy and later quickly copy this in a main requirements notepad which I keep for the requirement understanding.
Do the next thing next. That’s a pretty good rule. Read the tiny ad, that’s a pretty good rule, too.