Sprint Pre-Flight Checklist

One of the main feedback received in previous DESC Sprint Weeks is that advance preparation is key to a successful sprint.

This checklist is a tool to help you check that you have covered all the basics and that your sprint is good to go!

Sprint Description and Planning

The description of my sprint proposal is detailed enough to allow potentially interested participants to understand the goals and deliverables of the Sprint.

I have added all relevant labels to my Sprint issue, e.g. relevant working groups.

I have identified clear and manageable tasks that participants can start working on on Day 1. (You can for instance use checklists in your GitHub issue to lay out these tasks.)

I have advertised my sprint by linking to my GitHub issue in the relevant WG or TT Slack channels.

I have already reached out to people who could help in my sprint (e.g. by @ing them on the GitHub issue) to start assembling my team.

Logistics

I want my sprint to be hybrid (i.e. with both a significant number of in-person and remote participants).

An hybrid sprint (as opposed to mainly in-person or mainly remote sprints) requires additional preparation to ensure remote participants feel included and all participants can communicate easily. See this page for additional suggestions.

I have reached out to the Sprint Coordinators/LOC on Slack to request special equipment (omni-directional microphones, OWLS, dedicated room, etc).

I plan on staying mindful of inclusivity of remote participants, for instance making sure they have a chance to speak up during discussions.

I have added the Format: Hybrid label in my sprint description.

I have added the schedule for this sprint to my Sprint description (what day(s), what time), and used day labels to advertise this schedule (e.g. Monday).

I have prepared a communication channel (e.g. Slack channel) for my sprint and advertised it on my Sprint description. It can either be an existing WG or TT channel, or a new channel for this sprint.

New Participants Accessibility

I want to make my sprint accessible to new participants (recommended).

I have included background information on my Sprint description (e.g. link to tutorials, notebooks, slides).

The beginning of my sprint will explicitly contain a tutorial or "getting started" component to onboard new participants. I can task a particular expert sprinter to take care of this onboarding if I expect to be too busy with coordinating efforts.

I have advertised my sprint as new-contributor-friendly with the relevant github label.

Once you are down filling the checklist, click the button below to get your badge and advertise how well prepared your sprint is to other participants!

If you want to continue to prepare, here are some additional resources you might find useful: