Team leadership
I had two chances to lead a team in my life. Both times I created cross-functional teams of highly-skilled professionals from scratch — teams that I can be proud of.
After receiving a PhD in Technology, I got my first team as a Head of research department in the Information and Communication Center of the research institute. I had to build my own research team for automated systems design. I achieved such good results building a team of IT professionals and a test lab infrastructure that some time later I was assigned as Head of the IT department of the institute. While staying as head of the research department, I managed both system administrators and researchers. That was a very interesting experience for me: I had a chance to participate in scientific projects and help people practically, both times being tasked with dealing with IT problems. That period was very important for my development as a multi-spectrum specialist and a good manager.
My second chance to lead a team happened at my then workplace, when I was asked to form a new documentation team for VK Cloud Solutions (Mail.Ru Cloud Solutions at that time). I had been working in the company for more than a year already. This was a great chance for me not only to build a new team from scratch but also to improve my leadership skills in an Agile environment. My previous experience was in classic management (also called the Waterfall method). Since then, I have created and managed a team of 11 professionals in different areas: 5 technical writers, 4 analysts, 1 QA, and 1 DocOps specialist. I established effective processes with regular (daily, weekly, and monthly) meetings, short-term (one sprint) and mid-term (1–3 months) planning, sprint retrospectives, style guide discussions, and regular feedback exchange.
I am also the leader of the technical writers’ guild in my company. It is a professional group with regular (bi-weekly) internal meetups and discussions for experience exchange.