Skip to content

Latest commit

 

History

History
64 lines (43 loc) · 4.8 KB

meetings-purpose.md

File metadata and controls

64 lines (43 loc) · 4.8 KB

iOS Chapter Meetings

As an engineer part of the iOS Chapter Team we have to collaborate with each other. The work we do in our squads contributes to the whole product and at the end of the Sprint we are all releasing the same app, together as a team. We should all be focused in delivering the work assigned from our squad and at the same time try to engage with the other iOS Engineers to keep the communication channel open and make everyone feel comfortable to raise any comment/question. We have scheduled a set of iOS Team specific meetings to ensure we communicate with each other, raise any issue, announce important events and are aware of the process and follow it.

All the outcomes from these meetings are posted in the #ios-meeting-outcomes Slack channel along with their recording.

iOS Retro

The place where we can raise anything that went well or should be improved in our last 2 weeks of work. This can be anything related to the iOS Team in general or something from our Squads in particular but we feel relevant to raise.

Some of the issues you have in your squad are common to other squads. Those can be raised in this meeting to understand if it’s something that can be addressed. Additionally, the good achievements we have in our squads can and should also be raised in the retro so everyone is aware of the good work everyone is doing.

This is a fortnightly meeting with 30 minutes duration. The schedule is the following:

  • For 2 weeks the board will be available in the Trello iOS Engineering Team (Please look for the board with the title "Retro <Date of the Retro>") so we can add items at any time during those 2 weeks.
  • The first 2 minutes will be for us to vote. (Tip: Hovering over a card and clicking "v" will add or remove a vote.)
  • The rest of the minutes will be to go through the most voted items in the Went Well and To Improve columns and add any required action to the Action Items column. Each action has to have someone assigned to it.

PR Parties

[IMPORTANT] The recurring PR Party meetings are now cancelled given the low number of PRs opened for review at the same time. PR Party meetings can still be be scheduled when needed.

The PR Parties are groups of engineers who are assembled to review a bunch of PRs they're assigned to. Usually the authors of these PRs will be in the group. Participants will start by reviewing PRs asynchronously on their own. If there is a need, a meeting will be organised where the authors will go through their PRs and explain them. This will open a discussion about them and a different approach can be agreed on if required. In an ideal world, we would have all the PRs approved by the end of the meeting, but this is not the main goal. The purpose is to facilitate the discussion about the PR implementation.

A PR Party Line-Up will be announced every Monday, Wednesday and Thursday.

  • The Line-Up will be posted in the #ios-meeting-outcomes Slack channel.
  • Each PR Party will be composed by 3-4 engineers and will have 3-4 PRs to review.
  • If a meeting is needed, the schedule and duration will be decided by the group.
  • One of the engineers in each group will be the organizer (nominated by who defines the group). The organizer's responsibility is to:
    • create the Slack channel with the other participants
    • make sure a schedule is defined
    • kick-off the meeting if needed
    • post the outcome in the thread of the PR Party Line-Up message in Slack.
  • There is an exception in the final week of each sprint. The Main PR Party on Thursday will still happen to accelerate PR Reviews for release. In these weeks there will only be 2 sets of 2 groups of PR Parties.

iOS Lunch & Learn

The purpose of this meeting is to have fortnightly iOS learning sessions with the whole team. We will grab lunch before the meeting, sit together (physically or remotely) and:

  • Watch a video relevant to the iOS team.
  • Watch a presentation done by someone in the team (full or lightning).
  • Have a discussion about a topic that impacts the iOS team.

Every meeting has an organizer who is responsible for:

  • Setting up the zoom call
  • Book a room if in the office
  • Define a topic.

The schedule can be found here.

Topics to be picked up can be found here.

Banter

An unstructured meeting happening every week for 30 minutes. It is the place for us to speak about any topic we would like, can even be something completely unrelated with work. It is frequently used to make small announcements and have small discussions around a recent event. This meeting is optional.