Weekly Team Meetings

These meetings take place every week and last for an hour.

Use this time to talk about any issues that affect you and your team from the past week. These include but are not limited to:

• Issues that have popped up multiple times.
• Topics that have continued to remain relevant or have yet to be solved.
• Items that have gained importance due to project priority shifts
• New projects on the horizon
• New SOP that need to be followed
• Communication patterns (positive or negative)
• Praise for completion / solution of engineer or team

This time could also be utilized by engineers who have an important topic that they would like to bring up with their fellow engineers. Of course, the type of discussion as well as length is up to you.

When creating a team-meeting, it is best created beforehand to ease the flow of information. One reason why this is essential is that it prevents the presenter from typing long sentences in one post, leaving the engineers looking at "X is typing" for an inordinate amount of time.

Check out our example of a Weekly Team Meeting to get a sense of what its structure looks like.

One important aspect of conducting this meeting in a text-based environment is permanence. Permanence is something that is often overlooked when discussing the pros and cons with methods of communication. Here the Team Meetings never disappear. The dev is free to go back in time and look at the notes given in these discussions as well as other discussions had in the past. This makes problem solving, user accountability, and information gathering much easier.

We recommend creating a google doc from which to add information to during the week. This same document can then be utilized in the following week as a resource when structuring Team Meetings.