Team Meetings

You and your team need to meet at least twice per week and keep minutes of these meetings. Everyone is expected to attend team meetings.

Types of meetings

There are two main types of team meetings:

1. Planning meetings to plan your next activity.
2. Status meetings to check-in with the team and make sure that nobody is blocked on their work.

Planning meetings

The first day of any project activity should start with a planning meeting where you do the following:

1. Agree on your objectives for the upcoming milestone e.g., “this is sprint 2 so we need to plan the structure for the user interface”.
2. Agree on the actual requirements that you will address as part of that main objective. e.g., “We’ll implement the main Views for the application, so that every screen loads, and we can navigate between them. However, none of them need to work yet.”
3. Make sure that there are issues logged for each requirement and assign them to team members. e.g., “I’ll do the Search screen, and Amanda is handling the Login screen. Jeremy can you to the main details views?”.

The outcome of this meeting should be:

• A fully assigned list of issues for the deliverable (sprint).
• Meeting minutes to record who was present, the main objective of your upcoming milestone, and link to the issues list (don’t repeat the entire list of issues in your meeting minutes, you can just link to the milestone view).

Status meetings

These are just check-in meetings to make sure that the project is on-track. Scrum does daily checkins, and while we won’t be adopting that practice, these are meant to answer the same questions.

• Is everyone making progress on their issues?
• Does anyone need help? Are you stuck? (This is the time to identify and address problems, not the day of the demo!)

Often this can just be a brief round-table update from everyone. It’s also a good opportunity to get feedback from your team. e.g., “Amanda: I have the Login screen mocked up in Figma, and here’s what I’m implementing. Does anyone have any comments or thoughts on how to make it more usable?”

The outcome of a status meeting should be:

• Meeting minutes to record who was present, and a brief update (“Everyone is making great progress” is an acceptable update if it’s true! If every meeting ends like this, you are probably not digging into issues enough).
• Updated issues list. You should avoid assigning new work to people, but its not uncommon to reassign work i.e., Jeremy’s major issue ended up being solved in 20 mins, so you can give him one of Amanda’s UI issues to work on.

Meeting Minutes

These team meeting minutes can be brief, but should document any significant decisions that the team makes.

• You should have a link from your README file to your meeting minutes.
• The meeting minutes should be stored in a single wiki page, and have this format: