S62 Retrospective

Date	Jun 7, 2023
In sprint	@David Trapp @Mwayanjana Bolokonya (Unlicensed) @Javier Antonio Hernandez De Paz @Carolina di Lello (Unlicensed) @Duncan Brain @Sayaka Ono @Joyce Sato-Reinhold @Denis Dovganyuk @jeremy.bennett8 (Unlicensed) @Cedric Levasseur-Laberge (Unlicensed) @Gursimran Singh @Iván Perdomo @Lite Farm
At retro	@Lite Farm@Denis Dovganyuk @David Trapp @Duncan Brain @Joyce Sato-Reinhold @Sayaka Ono @Mwayanjana Bolokonya (Unlicensed)
Recording	Posted in Slack

Background

This retro is for the S62, roughly: Thursday, May 29th - Wednesday, June 7th

Please add comments before the meeting! We’ll take a few minutes to add additional comments and discuss, then put together action items to operationalize suggestions.

Last sprints (S61) retro is here: S61 (Sensor patch) Retrospective

Retrospective

Discussion topics:

Your topics here…
- How are the modifications to sprint routines and rituals landing with people? Anything else we should adopt?
  - When should we be responding to the asynch bot? At any point before stand-up is fine
  - @Joyce Sato-Reinhold misses having the post-planning ticket estimation - will this be a part of tech daily on the Friday after planning?
Tech daily and / or daily stand-ups
- Tech daily is a deep dive
- Daily stand-up is a quick snapshot for the day

Start doing	Stop doing	Keep doing	Shout outs

Start doing	Stop doing	Keep doing	Shout outs
Send API errors to Sentry (currently only picking up exceptions from webapp) Add whatever you can to #contrib Think through how modifications to access will impact folks outside the core team Figure out how to get contributors into tech dailies We could have certain days for core team and certain days as “office hours”. Alternatively, we could open up every day and just have a set agenda on certain days. @Iván Perdomo please weigh in.		Tech dailies! Should daily stand ups change to accommodate? Seem like very different purposes - so NO! Commitment to code quality, working together with reviews to bring our highest quality and low error code	@David Trapp for smoothly pivoting to a fairly different outreach strategy with grace and enthusiasm @Denis Dovganyuk for being tireless in the pursuit of bugs @Sayaka Ono for diligence and competence @Iván Perdomo for leaping in with both feet @Javier Antonio Hernandez De Paz for exceptional critical thinking

Action items:

Investigate routing API errors to Sentry @Mwayanjana Bolokonya (Unlicensed)

During S63, @Mwayanjana Bolokonya (Unlicensed) investigated and began implementing it on Beta. @Iván Perdomo, it is active on Beta, but need to add the DSN when we add it to Production. Ticket number is LF-3359.

How to open up tech dailies to the community? @Iván Perdomo

@Iván Perdomo, proposes that we open it to the community ad-hoc. For example, we’ll have a session on DORA Metrics, which we’ll open to the community. But currently, would prefer to keep the dailies as they are with only staff present.