| title | description |
|---|---|
Open Standup |
How do we do whole-team standup at Artsy? |
We've been doing engineering stand-ups for as long as there has been an engineering team. The format has changed over time as the size and scope of Artsy has changed. We're now on our fourth iteration of this process, which you can read more about here.
The current on-call engineers run standup. On-call rotations are staggered so an engineer starting on a Monday will team up with the engineer that started the preceding Wednesday. Pick one person to do the talking parts (facilitate the meeting) and one person to take notes.
The person handling the talking parts does this stuff ten minutes before standup:
@heres the dev channel. Include where the meeting is in the NYC office (usually the Annex).- Make sure on-call staff are prepared to give an update about the past week's incidents. (if you were on call, great! If you weren't, remind your partner.)
- Check the Knowledge Share schedule.
- The meeting starts with props (as a nod towards People are Paramount) and you should begin with giving props of your own.
Important: Make sure the person taking notes doesn't have their laptop next to the Zoom speakerphone.
The person who is facilitating the meeting should use the template below as an agenda.
These notes are then copied into a Notion document, and the link passed into #dev on Slack after standup. Everyone else leaves links to things they have commented on during the meeting, if they don't, we chase them up.
Finally, review this document for ways to improve the instructions for next week's meeting.
_Props_
-
_Company Updates & Important Communication_
-
_Practice Updates_
- Mobile:
- Web:
- Platform:
_On-call Support Updates_
- This week, @personC and @personD will be on-call for support until Wednesday, when @personE rotates on.
- Last week, we saw the following notable incidents (please include follow-up details).
- Incident Review schedule has N postmortems to review, next meeting is on X Day with @personZ as the speaker.
_Cross-dependencies / Requests for Pairing_
-
_Open RFCs (see #dev for list 9am EST on Mondays) or technical plans under consideration_
-
_New Milestones / Repos / Blog Posts / Podcast Episodes / New features or updated functionality released: prompt Amber, Diamond, Emerald, Onyx, Sapphire_
-
_Knowledge Share_
-
_Closing Announcements_
-
_Optional: Q&A / Open Discussion_
-