S102 Retrospective
Date | December, 18th 2024 |
---|---|
In sprint | @Denis Dovganyuk @Larisse Cavalcante @Duncan Brain@Joyce Sato-Reinhold @Loic Sans @Divya Chayanam@Anto Sgarlatta @Sayaka Ono @Navdeep Dhammu @Gursimran Singh |
At retro |
|
Recording | Not recorded |
Background
This retro is for S101:
Thursday, December 5th | Wednesday, December 18th |
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 (S101) retro is here: S101 Retrospective
Discussion topics:
Consent Forms
Process
English only is updated ahead of release
any reason it was at the end of release? Can we do this at the very start?
Let crowdin handle the rest
Potentially quite an extra effort for both teams by choosing google docs vs crowdin
Lets re-test? Tested live on call and CrowdIn works as expected highlighting changes.
CrowdIn should be used for translations of consent
Out of sync in es, fr, pt
A few paragraphs need reconciling about what the correct translation is
Bug bash timing
Duncan wasn't able to send out tickets to contributors as sprint facilitator, tough to know what to give them
Can we move up bug bash to have the weekend knowing what is blockers on friday before weekend?
Bug bash improvement suggestions
Better definition of blocker vs nice to have
Blocker-Low priority does not make sense
Can we have hard stop blockers and priority levels on nice to have?
Swag or prize incentive for bug bash ”winner” as decided by bug bash officer
Start doing | Stop doing | Keep doing | Shout outs |
---|---|---|---|
engaging contributors for bug fixes before the release remind contributors that our users have never seen the module as well so fresh eyes are useful - communicating the learning value of finding bugs for code contributors |
|
| @Anto Sgarlatta for keeping us on track with release schedule! Seconded! Everyone, for the animals release! Fantastic work, livestock module is finally out! @Loic Sans for quick turnaround for the designs and the numerous questions answered @Denis Dovganyuk for identifying all the issues and bugs efficiently, as usual! |