Date: 16 Jan 2023
Participants: @Luke, @Han, @Leia

Issues & epics

Action items (previous retrospective)

• Update the roadmap for our technical debt: @Luke

• Revise the team handbook based on the results of the team discussion: @Han

• Update the release process to prevent unverified items from rolling over to next RC: @Leia

Retrospective

What went well

• We were able to accelerate delivery of certain features thanks to community contributions and collaboration.

• Newly onboarded engineers are doing well and have been collaborating well with each other and existing members in order to solve problems.

• The release process has become well-documented and ran smoother than it ever has.

What went badly

• We regularly are starting work on issues that turn out to take several months to complete. Sometimes we realize midway through we could have broken down issues into smaller deliverables that add value on their own.

• We still don’t have a reliable way to test large data sets.

• Changes were made to planned feature releases at the last minute. Created scramble to change the blog post, home page, and tweet, etc.

Ideas for improvement

• Be more proactive with communication on issues that stay open for a while.

• Communication needs to happen in public channels, such as Nuclino, not via DMs, to make sure we can all work together in getting our deliverables done.

• There is some tribal knowledge in our team that should be documented to help with onboarding and knowledge sharing generally.

Action items

• Create 2-3 examples of Good code reviews to help set expectations of newly hired engineers around what our process looks like when it's functioning well: @Luke

• Better define the security release process, make it repeatable, and document in the Handbook: @Han

• Investigate time series data about regressions per release: @Leia