Skip to content

Latest commit

 

History

History
105 lines (70 loc) · 3.78 KB

open-standup.md

File metadata and controls

105 lines (70 loc) · 3.78 KB
Raw
title description
Open Standup
How do we do whole-team standup at Artsy?

Dev 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.

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 run the talking parts, and one person to take notes.

Ten minutes before a standup

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 Classroom).
  • Remind last week's on-call staff in #dev to prepare their updates about last week's rotation. Something like:

    @personA @personB reminder, we're looking for a list of major or notable incidents from last week during standup.

  • Check the Lunch&Learn schedule.
  • Think of who you'd like to give props to.

During standup

  • Important: Make sure the person taking notes doesn't have their laptop next to the Zoom speakerphone.
  • We start off with props, as a nod towards People are Paramount
  • Then we get an update from the VP of Engineering
  • Then an update from the Product managers (someone should be present to give one)
  • Then we get updates on new hires, people starting this week, newly accepted offers and etc.
  • Then we get an update about what the practices are currently thinking about
  • Then an update from last week's on-call support team, including follow-up work items
  • We leave a spot for potential cross-team issues
  • We list any open RFCs (see Peril's Monday morning post in the #dev Slack channel or here on GitHub)
  • We have a Milestones spot to talk about things people are proud of
  • We then either announce the Lunch & Learn, or try find one for the week
  • Anyone is free to give closing announcements, or props!

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.

Our Markdown Template

_Props_

-

_Company Updates (VP of Engineering)_

-

_Product Manager Updates_

-

_Hiring Updates_

-

_Practice Updates_

- Front-End:
- Front-End iOS:
- Platform:

_On-call Support Updates_

- This week, @personC and @personD will be on-call for support.
- ## Last week, we saw the following notable incidents (please include follow-up details)

_Cross-dependencies / Requests for Pairing_

-

_New Milestones / Repos / Blog Posts / New features or updated functionality released: prompt Auction, Gallery, Platform, Grow, Discover, Purchase teams_

-

_Current team-wide RFCs_ (see #dev for list 9am EST on Mondays)

-

_Lunch & Learn_ || _Show & Tell_ (if you don't know, ask in #lunch_and_learn or #dev-show-n-tell)

-

_Closing Announcements_

- The last two support engineers should stick around to chat with us, the new support engineers after this meeting.
- We'll also be having the front-end office hours right after this meeting, so stick around if you have questions.
-

Once you're done, follow the instructions in Notion on how to add it to our archives.