# T-compiler memshrink sprint retrospective

## Announcements

## Wins of Note

* Oli's calls were great
* Overlapped EST lunch time (but that's okay)
* Might be good to provide distinct/staggered timeslots to better accommdate various time zones

## What worked

## What didn't work

## What should we change for future (presumably remote) sprints

* Consider making it longer? (Two weeks?)
* Need more upfront planning: Goals *and* steps to achieve them.
* Perhaps structured as github issues, written in way ready for someone to pick it up and run with it.
* kickoff meeting on day 1 (either zulip or video chat)
* mentorship?
* during any given topic-oriented sprint?
* or have distinct mentorship-oriented sprints?
* dedicated github label for PR's related to the sprint