22Mar

3 Simple Ways to Engage With Your Remote Development Team

March 22, 2021 Jeremy Rouet 4

Jeremy Rouet

by Jérémy Rouet

3 Simple Ways to Engage With Your Remote Development Team

Your remote software or web developer group is one of the teams you would want to touch base with regularly, while at the same time giving them a peace of mind to concentrate on their work. A productive team of developers needs to put together their tools and visualize their goals. By uniting them, communicating with them, and keeping track of the latest product updates, you’ll be influencing their critical decisions and solving the common challenges associated with remote work.

Below are the 3 ways you can use to engage, build connections, and help your remote development team deliver the best for your company.

Share Updates Conveniently

Software developers will rely on your feedback to make changes to the app/website, whether in the development or testing phase. You want to keep in touch with them, so their work becomes easy and bearable. If you take a week to give feedback, and another one to update them on your website’s preference – the team will drift off course.

This is where you can take advantage of our Weet platform – instantly receive notification from your remote developers, and reply with customized feedback. With Weet you can share quick updates by sharing your Weet video with your busybees. They will get an email notification and check on your update at a time most convenient. Maybe you’re thinking of showing the developers how you want the company app or logo to feature certain graphics. This you can do by sharing a screen with samples or using short descriptive videos.

Define Goals and Communicate Regularly

To set up your remote development team for success, always set clear and measurable goals. Individual members of the team should be responsible for giving updates and coordinating specific sections of the project.

Like in many remote teams – where a crucial message can get lost in translation – often prioritize assigning duties and responsibilities. This makes each member of the team accountable for meeting the set standards and respecting deadlines.

Use Visuals and Interactive Features

To keep your remote developer team engaged, you should add some fun to the communication process. Make the connection lively and entertaining. Whether you’re requesting for an update or you’re giving them a heads-up to proceed to the next phase, always focus on building rapport. Weet has collaboration features like use of emojis, background filters and responding via texts to keep the communication engaging.

For your developer team to pass the message across, they need to use visuals, videos, graphs, and screenshots, or even share screens. You want to converge on one channel where you can share the ideas while keeping some of the information private and safe.

Conclusion

Your remote developers want to be part of your company’s decision-making team, but they need your approval. They want to proceed with caution and always have you satisfied with every step they take. This can be overwhelming without the right collaboration software.

Luckily, we have a tool where you can grant your remote teams the stage to have a word and be heard. Our Weet platform has been designed to overcome remote communication barriers. The focus here is to make it convenient for your remote developers to communicate with company leaders, keep up with the latest company updates, find all the materials, and access relevant information – all these, without having to look around.

The async video meeting that frees up your agenda

Get Weet for free

29Oct

How Video Messages Help Us Explain and Review Code

October 29, 2020 Jeremy Rouet 15

How Video Messages Help Us Explain and Review Code

by Jérémy Rouet

How-Video-Messages-Help-Us-Explain-and-Review-Code

At Weet, we have witnessed significant improvement in asynchronous communication using Weet, our video messaging tool. Our team’s performance, as well as that of the product team, has greatly improved. Our new video messaging tool has provided a more impactful way for our engineering teams with less ambiguity, and communication with more context. These impactful code reviews would have been impossible without a combination of both narrative and visual context. Let me share the new features;

With the new Weet 2.0 release it is easy to track your sections and time them for your preference. Our AI has determined 2:30 is the ideal section length but additional options are available.

Now you can preview your screen recording before finalizing a weet to share with your team. With the timeline section player you also get a play by play.

Also, unlike other online screen recording tools, Weet allows you to co-collaborate with your teammates by using webcam, audio or rich text reactions.

Code Reviews

In the event of a new project, or changes implemented in the workspace, employees may ask for further clarification on the issues at hand to further their understanding. This is also an opportunity to brainstorm, increase workplace productivity, and disseminate further information on the project at hand.

We now use Weet videos to prepare for and conduct code reviews. For example, we record a code review in a Weet and put the link directly in Gitlab and GitHub.

According to Baseline, the motivation behind code reviews is to improve code quality. Every change, bug fix etc. must have a specific reason and offer a solution. Weet enables the flow of the code review process by allowing screen share and explanation with audio and/or webcam for an effective collaborative process.

Provide Insight on How a Feature Is Built

At times we want to build a feature that our user can see and interact with comfortably; therefore, we open a code review. It may turn out difficult, explaining how the code we’re reviewing relates to matters such as interactions and interface. To illustrate this, we use Weet to clarify before the code is reviewed.

Provide Investigative Context

We always find it useful to have a story on the process, especially when fixing a bug or issue. We focus more on the underlying development, investigation, and improving process, which may be complicated. Using a weet, we can spread communal knowledge as well as learn more information on a fix. This makes reviewing the code more productive.

Effective Guidelines on How to Set up a Repository

We have faced a common issue in setting up a new code repository and getting it up and running. Text instructions have been used as the most common set up steps. However, using the weet video helps us provide more detailed instructions on setup commands and how to fix common installation errors.

Explain Architecture Diagrams More Suitably

We have been using architecture diagrams in our documents to explain information flow on our systems. However, we found out that using weet is much faster to redirect someone onboard our new system.

Weet has saved us the hassle of memorizing how an architecture system works and reading our wiki diagrams. Using weets, engineers can easily read the diagram and review the story on how we landed on the enactment. They will then engage us in questions from a deeper level of understanding. This helps save time, which would have been spent explaining written copies.

Detail Debug Flows

Weet helps eliminate explaining repeatable steps that make it long to debug a problem. Text instructions with steps may tend to get more complicated when the debug flow gets complex. The steps become even hard to follow through over a text. By use of a weet video, our engineers find it easy to help debug the problem.

Help Others Navigate Complicated Pages More Conveniently

Some of the pages are just too complicated to navigate. This is a problem we come across too often. Our weets introduce users to detailed documentation that enables them to navigate to the information they are interested in at ease.

Enhanced Way to Report Bugs

It’s so hard transferring what we see to text. We also identified a loss of clarity when trying to write up what we see. Text has been considered great, but at times it may not be precise enough. At times we want more information that explains a bug report on what is happening to fix it.

There is a loss of important information when transferring content from what you experience to text. It’s also hard as our support team may be using different terms to explain a bug issue. We have found great support in weet videos, which helps our technical and non technical teams fix bugs much faster. Weet saves on time.

The async video meeting that frees up your agenda

Get Weet for free

14Sep

Providing QA to Engineer Teams

September 14, 2020 Jeremy Rouet 13

Providing QA to Engineers

by Jérémy Rouet

3-Easy-Ways-to-Provide-Q&A-Updates-to-Your-Staff

The provision of QA to Engineers can be termed as a work in progress. There is always the back and forth consultation while working on the same product. The communication part is very crucial to achieve quality assurance.

Engineers and developers require constant communication to eliminate gaps. The whole process of product quality assurance(QA) needs communication at every step. Losing contact between engineers and developers is not an option. However, at times this may become impossible, especially when using calls or email with videos. While using calls and emails, you may forget an important detail that could hinder efficiency.

Get early access to Weet here.

Using Weet for Quality Assurance

Weet is highly recommended as a remote collaboration tool. Using Weet asynchronous communication, participants can easily follow through a conversation. There is also the screen recording tool that enables one to record their screen and share feedback. Using Weet fills the communication gap between developers and engineers. Here are features available on Weet:

A Systematic Arrangement of Video Messages

While doing QA routine rounds, Weet makes it easy to record videos and leave a description. The purpose of videos and labeling is to best describe the error spotted or task at hand. Weet also enables one to create folders systematically with titles and descriptions. The engineering teams can easily walk through each video. This makes it easy to solve a problem, and work is more organized.

An Enriched Way to Share Screens and Descriptions

Sharing of information becomes more challenging for engineers when using screenshots. While other screenshots capture the problem well, the description may be wrongly placed. There are also incidences when you need more than one screenshot to describe an issue.

This makes the engineering teams work hectic, figuring out the perfect flow. Screenshots also do not necessarily capture the error in high definition. At times linking screenshots wrongly confuses the whole team.

The use of Weet videos makes it easier to provide QA to products. Weet eliminates the need to share several screenshots and descriptions and reduces back and forth communication. By using the screen recorder tool, you can easily create screenshares in Weet. Weet videos provide a systematic flow making it easy for the engineering team to follow through. The engineering team will also find it easy to provide QA.

Weet Enhances Clarity

To efficiently test a product, you need to have a full understanding of the product. It should not be a case of trying to connect the dots. By the use of Weet videos, there is more clarity. Your engineering team can follow through every step without the need to ask for an explanation.

Effective Communication

Communication is a vital tool for any QA engineer. Having efficient direct communication between engineers and the product technical team is critical. Communication failure at any point may hinder the delivery of QA. Weet introduces an effective way to keep the communication flow going.

The use of Weet videos provides an accurate description of every step. The engineering team can also receive replies through audio, video or text. This makes responses much clearer and understandable.

Driving for Results

Providing QA is not a matter of only spotting the bugs. A reliable QA engineer needs to provide a solution. To drive for results, the engineer needs a tool that efficiently captures everything. After receiving the correct information from the development team, it becomes easy to take the next action course.

Weet drives for results by ensuring QA engineers receive valuable information that will help spot any bugs.

QA is quite essential to the engineering team. For an adequate response, the engineering team needs a tool that efficiently broadcasts the right information quickly.

Visit our updates post to read the latest in Weet enhancements.

The async video meeting that frees up your agenda

Get Weet for free