How to host sprint meetings

Intro

This document will walk you through how to host sprint meetings.

Goal

The goal of each sprint is:

1. Make sure every engineer is on the same page. By demoing each feature (in production) that were accomplished during the sprint, engineers get to see what each other worked on.
2. Call out big changes. If there are big updates that changes any engineering process, sprint is the time to talk about those to remind the team and make sure everyone is aware of the changes.
3. General bonding. Since everyone is remote, its nice to get together and hear each other's voice.

Link to current sprint

Link to previous sprints

Running a sprint

Before sprint

Ideally, make sure this current sprint document is updated first with accomplishments (merged in features / upgrades) since the previous sprint.

During sprint

After introductions, here are some ideas of things to go over:

1. Update the current sprint document if you haven't done it before the sprint.
2. Introduce new members who finished JS6 and were invited to engineering.
3. Demo (on production) new features / bug fixes that were merged in.
4. Discuss any process changes (if any) or general engineering updates.
5. Wait for someone to volunteer to lead the next sprint (we should rotate sprint host) and pick a name for the next sprint
6. Update the current sprint document with discussion conclusions (if needed)

After sprint

Update Announcements chatroom so that all users are aware of our updates.

Best practices

• No need to mention who worked on what during each sprint. The main goal is to highlight what was accomplished as a team.
• No need to assign issues to individuals during sprint. This adds stress, which is unnecessary especially because this project is volunteer based. Everyone should be working on the issues they want to work on at their own discretion.