Working with a remote team can be difficult. Reading this playbook will help you set up a Shinetech team quickly and smoothly from start to finish.
As a customer, you may be confused if you don't know our team members. It can sometimes be difficult to build trust at the beginning.The team may also have the same problem.
We believe it is essential to bring our team onsite to your offices. You will quickly get to know who is "Russel", "Jack" or "Alex".. Working together onsite facilitates the first trust. The team will also better understand your business requests. At Shinetech, we offer our new customers one week of onsite work without any additional cost.
You are also welcome come to our offices and work with team together. Face to face communication is very important for remote teams. Most of our successful projects began with our teams meeting clients, working onsite and utilising face to face communication.
Video meetings are also highly recommended once a week in a newly set up team. Voice calls are also very good for ad hoc meetings, stand up meetings or daily updates. All our teams can use Skype or GoToMeeting for voice or video calls.
When we talk about communication, culture plays a big role. The culture or the way of life can make some things different, even in the workplace.
Say “hello” or face to face welcome in daily stand up meetings, then you know that the team starts to work and the team knows you work,too.
If you are used to setting up away messages/out of office notes, it would be useful to notify your teams to do the same. Away messages are very valuable for remote teams. You are not in the same offices and people cannot see you. It would be very much appreciated if you could tell people that you are currently working or away.
Group talks are much better in a remote teams. It removes the need to transfer the requests or queries. It mitigates the risks of big surprises.
Some cultures have a thing call "Losing Face". Some developers may be shy to ask the same questions repeatedly. They may want to research deeply and try to solve the problems but still there can still be risks and inefficiencies. You may notice this if this happens - You might sense a change in body language or speaking tone. If you do notice anything, please feel free explain more or ask any follow up questions to ensure they fully understand.
When you and our teams set up good communication methods, you will be able to have more direct business requests rather than technical requests. It may be challenging at the start, but if done well, you will be enjoying your beach and beer.
Everyone will tell you they have experience with SCRUM or SAFE, even our teams, but you still need to find the best practices that fit your project.
Pair-programming is a great practice for remote works. Ask your team work with you as a pair. This will allow you to easily see their coding capacity. They will also be able to understand your code style, framework and current system. It is also a good way to let team understand your business logic, values and strategy better.
Sometimes you can even try Mob programming.
Keeping a working system is very good way for any type of project or product. You can use it for testing, review, demo or even pre-sell. Ask our team to build CI and CD environments, all team members can check daily updates and weekly or monthly releases.
It's very nice to let everyone know you are now working in a remote team. Face to Face welcomes are very good. You can do it in daily stand up meetings as well - Just turn on the web camera and say "Hello". You can also use a virtual office tool like Socoo, Slack or Screenhero. Everyone will know who is working and who will be back soon.
It's always good to know the team’s thoughts for the last iteration. Join the retrospective meeting and discuss the Top 3 good things and Top 3 things that need improvement. Be honest, be kind and the team will definitely listen to you.