This retro is to review the most recent release of LiteFarm, which happened on 21/11/2023.
...
Start doing | Stop doing | Keep doing | Shout outs |
---|
Being more proactive around making tech debt and bugfixing part of every sprint planning on top of having specific bugfixing/tech debt weeks Doing continuous translations rather than a massive list at the end of the sprint. (Loic) More specific process for translations? What happened to post-release vacation? (I never heard of post-release vacation? ) I would like to get involved in non-sensitive styling issues - ie: SASS or CSS (Loic).
| | 2 week release cycle!! (Unanimous agreement!!) Post release patch (they are easy, and fun – and the alternative is stricter code freeze) I want to validate all visual and user sensitive tickets (Loic) Dev control of the release process / checklist One day a week of plain focus. One reviewer per PR. Paid testers. Target Tuesdays (to Thursdays as necessary) for release
| I would like to say a huge thank you to the whole team for their support. Especially to Antonella for all her efforts to help me learn JavaScript. Anto Sgarlatta for leading our smoothest release process yet! (And also to patch team – we did really well too!) All the team for doing great work
|
...
- Review previous retro action items
- Look into Jira: is there a way to calculate and track the portion of time spent on feature vs tech debt Anto Sgarlatta
- Make sure each sprint has a few tech debt tickets, even when the focus of the sprint is feature development Anto Sgarlatta
- Try tagging Loic Sans and Larisse Cavalcante in open PRs for 1-2 sprints and re-evaluate @devs
- Meeting between Larisse Cavalcante and David Trapp and Joyce Sato-Reinhold to discuss this PR process
- Schedule all-team meeting on translation process (and do some research on alternatives processes and tools) Anto Sgarlatta
- Reinstate post-release vacation @team
- Anto Sgarlatta to discuss current implementation of app styling with Loic Sans during next 1-on-1
- Postpone tickets that require translation (unless completely critical) until after release @team