Spatial Retro - FY24Q1-2

 Overview

 

Date

Jul 28, 2023

Team

Spatial

 Retrospective

This time we will focus on how certain events or situations made us feel. We'll use these to talk about how we can improve our process going forward.

Mad

Sad

Glad

Mad

Sad

Glad

CJ: UI work is painfully slow

NS: Lots of changes (architectural and ui), difficult to keep track of, developing features before systems are ready (design and other systems)

CJ: Upcoming structure change seems to be generally good idea

TC: This week was a bit of a learning curve

YC: Miss Sean for the rest of the week

RH: Jit was a big help while I was away - thanks Jit.

NM: I am not mad this sprint

NM: Too many changes to digest

TC: We had a good planning session, it was great to brainstrom with the team together.

 

RH: I was away on leave for a while, which put more pressure on the design-front. Lots of catching up to do now.

TC: No more OpenLayers

NS: Broken linking after IA changes

YC: not detailed AC on refactor

NS: Lucky to have a great team

RH: Still no confirmation of an extra design resource yet.

RH: No dedicated design-system dev resource anymore.

 

YC: regression bug a lot but no traceability, not sure should go WF or Spatial?

 

 

 

 Action items

UI walkthrough with team @Ryan Herbert Aug 11, 2023
Discuss “design system” DEV in Spatial with WF team @Jacques.DuToit (Unlicensed) Aug 2, 2023
Any changes published (merged to Main) to a Teams channel (semantic releases): Nathen & @Jigar Sheth
Test on 4 major browsers (Edge, Safari, Chrome, Firefox) @Yusong Cheng
Regular Dev tech knowledge share. @Jacques.DuToit (Unlicensed) to socialise with other teams (cadence or ad-hoc OR Dev catch-u meetings on fortnightly cadence):https://nhvr.atlassian.net/browse/NSSP-5624