I've been a Remote Developer myself for more than 5 years now and a few things that I and my team have learnt the hard way, are kind of based on the above questions that we asked each other.
Yes Damien, you are right. Sometimes, the Written Communication can lead to be a miscommunication - if there is not enough understanding within the team mates.
I believe, we all have to understand that what matters is the people. If people can gel up with each other even after working remote, we will never face any such cases of miscommunication, because the person who is remote to the current person in context will understand what that person means in the email or the chat.
And the biggest thing that comes in picture is when we are working remotely, we might be working with people who have Different Culture and the words we use and are right for us, might not be for the other person.
So its very important to for the remote developers to understand each other and have a comfort-zone within themselves so that they can share what they want and are sure it won't be taken wrongly.
Daily Video Calls are the best -- whether its Scrum Calls, Dev Specific calls, calls with FED/BED, QA/DEV, Sprint Planning, Retrospective -- Any meeting what so ever -- As its good to talk to a Human Being rather than Talking to a Voice!
During such calls, or usual dev meetings, we start our meetings with usual conversations like what did you do this weekend? Or what's the weather like at your end? -- Such questions help understand each other develop a relation and this understanding is what helps teams working remotely tackle the problem of Miscommuncations.
Also, a regular 1:1 meeting with your Line Manager/Team Leader for a Developer or any team mate working on that team is a must -- and this is specifically true for a Remote Person -- as they might not get chance to share the story at their end -- and the Line manager needs to know what it is like working remotely, from the Remote Developer's perspective.
Again, there are cases where say for deciding an approach or architecture of some task, there are some email updates. If the email chain is going long one of the members in the email chain has to decide to schedule a meeting and finalize the stuff. If its just 2 in context, one should pick up the phone and call the other one up -- Talking about it solves rather than writing about a thing!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I've been a Remote Developer myself for more than 5 years now and a few things that I and my team have learnt the hard way, are kind of based on the above questions that we asked each other.
Yes Damien, you are right. Sometimes, the Written Communication can lead to be a miscommunication - if there is not enough understanding within the team mates.
I believe, we all have to understand that what matters is the people. If people can gel up with each other even after working remote, we will never face any such cases of miscommunication, because the person who is remote to the current person in context will understand what that person means in the email or the chat.
And the biggest thing that comes in picture is when we are working remotely, we might be working with people who have Different Culture and the words we use and are right for us, might not be for the other person.
So its very important to for the remote developers to understand each other and have a comfort-zone within themselves so that they can share what they want and are sure it won't be taken wrongly.
Daily Video Calls are the best -- whether its Scrum Calls, Dev Specific calls, calls with FED/BED, QA/DEV, Sprint Planning, Retrospective -- Any meeting what so ever -- As its good to talk to a Human Being rather than Talking to a Voice!
During such calls, or usual dev meetings, we start our meetings with usual conversations like what did you do this weekend? Or what's the weather like at your end? -- Such questions help understand each other develop a relation and this understanding is what helps teams working remotely tackle the problem of Miscommuncations.
Also, a regular 1:1 meeting with your Line Manager/Team Leader for a Developer or any team mate working on that team is a must -- and this is specifically true for a Remote Person -- as they might not get chance to share the story at their end -- and the Line manager needs to know what it is like working remotely, from the Remote Developer's perspective.
Again, there are cases where say for deciding an approach or architecture of some task, there are some email updates. If the email chain is going long one of the members in the email chain has to decide to schedule a meeting and finalize the stuff. If its just 2 in context, one should pick up the phone and call the other one up -- Talking about it solves rather than writing about a thing!