Skip to content

Latest commit

 

History

History
41 lines (30 loc) · 3.67 KB

sprint-rotation.md

File metadata and controls

41 lines (30 loc) · 3.67 KB
Raw
title description
Sprint Rotation
What is the sprint rotation and how does it work?

Sprint Rotation

Once an engineer has gone through general onboarding and done some basic set-up, they'll spend the following few sprints rotating through a variety of engineering teams.

Why rotate?

We want engineers to be familiar with the full breadth of products, systems, and people at Artsy, but at a comfortable pace. Rather than immediately joining a team for the long-term and focusing on that team's priorities, rotations allow engineers to tour the teams, get to know other engineers, and touch a variety of layers and systems. These rotations may influence the choice of team an engineer joins, or may just provide valuable context to their future work.

How do sprint rotations work?

Managers will arrange for new engineers to join a sequence of 3 or more teams for 1 sprint each. Emphasis should be on encountering a variety of teams and technology rather than having impact in a familiar space. Following these rotations, the engineer will join a team on a more stable basis.

Managers' responsibilities

  • Taking into account other rotating engineers and individual teams' schedules, managers decide an appropriate sequence of rotations and add each to the engineering onboarding Notion page🔒.
  • For each rotation, managers should nominate a "rotation buddy" from the team. A new hire's mentor is a great choice for initial rotation "buddy."

Rotation buddy responsibilities

  • You are the primary point of contact for the new engineer. Help them feel welcomed in the team and support them when they get stuck.
  • Schedule a 1:1 to get to know them and learn about their rotation expectations.
  • Ensure the new engineer is invited to all the relevant team meetings and team-specific channels.
  • Help the new starter set up any tools or projects that the team is using.
  • Collaborate with your team's technical lead to ensure a healthy backlog of good-first-issues.
  • Set aside time to pair with on good-first-issues or other tickets they are interested in working on.

New engineers' responsibilities

  • Engineers should join team slack channels, distribution lists, and events. You can join the team's google groups by going to this URL. If you have any issues joining the group, please let your manager know.
  • When possible, pair with your buddy or other team members on their sprint work.
  • When a pair isn't available, it can be useful to work independently on:
  • Schedule a convenient time (30 minutes should be sufficient) with the product manager to be introduced to the team's goals and metrics.
  • Schedule brief 1:1s with the other team members. Networking is an essential part of rotations. It enables you to get to know the organization through other people's experiences and understand what different folks in the team are doing.
  • The [in-progress]team process handbook🔒 covers many of the events and practices that are common among teams.