Hi, my name is tanya bizzitny and I'm the interim director of quality at get lab. I'm here today as moderator of the retrospective for a recent 13.12 release to provide you with a summary of the notes added to the retrospective by team members across r d. Let me share my screen, so you can see the slides great uh so I'll, be talking through four topics: praise for the team, what went well, what went wrong and what we can improve.

So, firstly, what praise do you have for the team? uh It is important for us, as part of our values, to say. Thank you next up what went well, a few themes I'd like to highlight are cross-functional collaboration across product groups and within the quad delivery of a few important pocs proofs of concept and demos, good velocity, even in one case, given a reduced team size and the benefits of maintaining a close eye on performance, regressions and iterating on performance analysis tools.

So next up what went wrong. There were a few instances of missing test coverage that allowed for bugs and regressions to show up. Additionally, we had some disruptive company-wide initiatives late in the milestone which impacted us delivering results, and next, how can we improve uh thanks to everybody who participated and really ensured that we were focused on improvement? This retrospective? This list is impressive.

The biggest themes I'd like to highlight are ensuring both synchronous and asynchronous communications are used effectively, uh reducing complexity to improve productivity and transparency and consistent workflow management during rapid actions.

So thank you for listening to my summary. I hope you'll join me when we meet as a team for the retrospective discussion uh monday june 7th at 1600 utc. We do have two discussion topics planned.

The first is around ways that people ensure the release post is accurate and reflects features that are truly available and done in time for the release, and the second topic is around tips and tricks for decision making when data is unavailable, such as what we experienced during our recent data replication lag during which many kpis were not up to date have a great day. Thank you.