S110 Retrospective
- Sayaka Ono
- Joyce Sato-Reinhold
- Denis Dovganyuk
Date | April 24 |
|---|---|
In sprint | @Loic Sans @Denis Dovganyuk @Divya Chayanam @Anto Sgarlatta @Duncan Brain @Sayaka Ono @Joyce Sato-Reinhold |
At retro | @Loic Sans @Denis Dovganyuk @Divya Chayanam @Anto Sgarlatta @Duncan Brain @Sayaka Ono @Joyce Sato-Reinhold |
Recording | Not recorded |
Background
This retro is for S110:
Thursday, April 10th | Wednesday, April 23rd |
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 (S109) retro is here: S109 Retrospective
Sprint Summary and Progress:
Our priorities for the sprint were:
Sensors: https://lite-farm.atlassian.net/browse/LF-4684
Pivots and Irrigation Prescriptions: https://lite-farm.atlassian.net/browse/LF-4759
Planned task / Jira issue | What is completed | What is pending | Notes Reason for delay: (requirement unclear, more difficult than initially intended / dependency / other). Please note this is to improve processes where there is potential.Status: (spill-over / depriroritized / rework) |
|---|---|---|---|
PR | Review | Reason: PR is large | |
Done |
|
| |
Some boilerplate | rest of functionality, tests, review | Reason: not enough time to start this one this week. Was moving the others through. I always forget about api tests, and typescript learning pains. Assessing what arch is already present. | |
Bulk of code | review + touchups | Reason: Needed part 1 reviewed to undraft part 2. | |
Reviewed the planned response body with ESci (Morten) Wed | Code! | Reason: was working on ticket below | |
2 PRs merged, 1 PR in review, rest of code ready (waiting on PR in review) | Last PR will need review, would like to touch base on design quickly today | Reason: Two short weeks, and two tangential complications (Google Map event listeners, which took ~a day, and troubleshooting our app-wide MUI theme for getting the interior MUI components working) | |
Most of coding | Part of LF-4768, needs adjustments | Reason: blocked Status: spill-over | |
Requirement clarification | Blocked by API, container | Reason: Just started, but it’s blocked Status: deprioritize? | |
Product
|
|
| For 1 & 3, dependency on individuals who are on leave, and picking up more urgent or important work instead of these
|
Design
|
|
|
|
QA
|
|
|
|
What went well | What could be improved |
|---|---|
Setting a sprint goal by assigning tickets during Planning? | Does reviewed and merged by end of sprint makes sense? |
Organizing my own time better (Anto) |
|
| Focus shift is challenging at times (Loic) |
|
|
Discussion topics:
Please add any topics that you would like to discuss with the team here:
[not urgent] - AI use and disclosure at work.
Use of AI is useful, but it helps to disclose the use so we know the extent people need to accept question it. Know where it is most useful and know where to restrict the usage.
Discussion call on different AI tools soon and possible ways to benefit individuals and LiteFarm as a whole
Policy for use of AI - where & how can we use / not use
Start doing | Stop doing | Keep doing | Shout outs |
|---|---|---|---|
|
|
|
|