Remote working experience

I work remotely more than 2 years already and would like to stress my attention on the following aspects of remote work:

Communication:

Fortunately, in the 21st century with the development of technologies we've got a lot of tools making remote work much easier than before. We use different online communication channels like video and phone calls, chats, dashboards for online collaboration, what makes people closer to each other, what is extremely important if you work in a team and responsible product delivery. You should know what's happening with your teammates and applications and react immediately to avoid any sort of issues.

Time management:

Remote work have taught me managing my time in a better way and respect time of my colleagues since most of us work in different time zones and have different working hours.

Documentation:

It is extremely important to have documented decisions stored online and keep them up to date. It is valid not only for onsite but for remote work as well, especially, when your colleagues are offline. So, as a manager, I pay a lot of attention to the quality of documentation.

Time to work, time to have fun:

Working onsite, we can organise some fun activities and we consider it as a normal thing. The same rule applies for remote work as well. We organise some online gaming sessions, kahoot quizzes or just talking about things which can make us closer as a team.


P.S. Working remotely doesn't mean sitting 8 hours in front of your desk every working day and doing your job, but it also means to be a part of the team, a part of the company, a very important part.

Comments

Post a Comment

Popular posts from this blog

QA Chapter

There are different point of view on organising a QA chapter. As a QA manager, I see it in the following way. If you ask me ` How  should  QA Chapter look like?` , I would suggest the following structure: Chapter Lead: Person taking final responsibility for decisions Mandatory: 3 QA engineers, 1 BE engineer, 1 FE engineer Optional: Product Owner, Architect, DevOps engineers NOTE: It is very important for me to have representatives of different roles in the chapter, since everyone sees how to improve quality and where to apply improvements differently.  If you ask me ` What  are  QA Chapter  areas of responsibility ?`, I will answer that the agenda of QA Chapter meetings should be based on the following areas: Product quality: Quality of Development Quality of Testing Quality Control Quality of Delivery Visibility of QA work If you ask me ` How are you going to make your QA Chapter performing well?` , I will answer that we will need to define a set of rules and constantly monitor tha
Read more

Leader is not an individual contributor

On many interviews for the leader's role you can hear questions like:  - Who pushed for this change? Who proposed this improvement? Who implemented this approach?  For me personally, leaders should answer in the following direction: - My team! It was a team effort! It was proposed by an individual, but implemented by the team!  Unfortunately, in many cases interviewers want to hear:  - It was me! I did this! It was my initiative!  They want to see an individual contributor pushing for changes and doing mostly a hands on work as a leader. Most likely, in their environment they need such a person.  My point of view, is that leader is a buddy, who can organise, motivate, inspire people. Sometimes he should lead by example, sometimes he should explain your fault one on one, sometimes he should motive a whole team. From day one in his role, real leader should start thinking about finding another leader in his team, to be able to delegate and share work with team mates. Only then you wil
Read more

Organizing UI automation testing

In recent years it is becoming less and less companies where you can meet dedicated test teams working with different development teams under the same product. This is most likely due to financial reasons because there are not so many companies who can afford to keep a team dedicated exclusively to testing and everything related to it. Nowadays a majority of software development companies work using Agile & Scrum, where all team members (software engineers, architects, programmers, analysts, QA experts, testers and etc.) are sitting together and doing their best to meet the goals of the sprint. In such projects testers, in principle, may know nothing about work of their colleagues from other teams because their areas of responsibilities intersect not very often or do not intersect at all. It can work fine until we are not starting talking about organizing automation testing and everything related to it: planning, design, implementation of frameworks and tests, support. I
Read more