Retrospective Feb 11 - Feb 22 (Sprint 34) (What needs improvement? (hard…
Feb 11 - Feb 22
What needs improvement?
hard for newcomers to start working on the projects
click and conversion server in ID was unstable for hours after release
performance problem still remains with the new Insights reports
frontend cache busting still not complete
development speed dropped compared to the previous sprint
dependency between cards caused some delays
didn't do the actions decided in the previous retrospective
What actions are needed?
keep a limit of improving existing code when developing in the legacy codebase
keep the code style and naming conventions of the new codebase when writing code
create card for enhancing the frontend cache busting
monitor 5XX responses of the tracker load balancers
Improve RDS data sync job to delete old data
set up daily build Jenkins jobs for the legacy and new systems
implement common code parts in separate small pull requests and review them fast
What went well?
progress of Global AT is still on track
ready for starting campaigns in Malaysia
code cleanups in the legacy codebase
Huy's contract is finalized!!!
current bottleneck is fixed for the tracking system
no one was waiting for a new task idly
stayed healthy during the sprint