Squad Rotation

Hero image for Squad Rotation

Whether rotations occur according to the standard six-month schedule or punctually due to new project needs, the re-assignment of developers is common to most projects. To reduce the downsides of rotations, we have devised internal processes comprising two main phases and requiring the involvement of both the Product Manager and the Developer team.

In terms of duration, each phase corresponds to one sprint - usually two weeks. Therefore, an efficient rotation is a one-month effort.

Phase 1

Product Manager Responsibilities

  • Introduce the project to the new squad members.
  • Set up and/or request all required accounts and credentials for the new squad members.
  • Ensure the new squad members have write access to the code repositories.
  • Introduce the new squad members to the client.
  • Invite the new squad members to join the sprint planning session along with the current squad members.

Team Lead Responsibilities

  • Transfer of knowledge between Team Leads.
  • Keep assigning the User Stories to the current squad members.
  • Add the new squad members as code reviewers on all new pull requests.

Developer Responsibilities

  • Set up the codebase(s) in their local environment and ensure they can run it.
  • Continue performing code reviews on the project that they are phasing out of while starting code reviews on the new project. It will help them familiarize with the ongoing priorities and challenges but also with the codebase.

Phase 2

Product Manager Responsibilities

  • Include only the new squad members in the sprint planning session.
  • Ensure the User Stories for the current sprint have been assigned by the Team Lead solely to the new squad members.

Team Lead Responsibilities

  • Assign the User Stories to the new squad members.
  • Ensure the swift completion of User Stories and pull requests by the departing squad members.
  • Ensure the new squad members are in close proximity in the office.

Developer Responsibilities

  • Wrap up in-progress User Stories and pull requests on their current project until full completion. No unfinished work must be left behind.
  • Work on the User Stories in the new project.