Background
This retro is for S58: Thursday, February 23rd - Wednesday, Mar 8th
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 (S57) retro is here: S57 Retrospective (2023-02-22)
Retrospective
S57 Discussion topics:
Thoughts on an official process for verification refactoring? Duncan Brain
Especially for transferring ownership tickets and non-trivial refactors? (for example Irrigation task refactor, sensor readings refactor) it can be hard to pick up someone's work at 95% complete and to know what the last 5% is without specific guidance.
Problem: it’s hard to know what the right scope for a refactor is since it can be like peeling an onion
Proposed solution for refactors require the following definitions:
Any bugfixes that need to be made as part of scope
Latitude to make wider ranging architectural changes within a certain estimation (e.g. 1 - 3 points)
Documentation in additional tickets of any other bugs / recommendations found that weren’t in addressed in i or ii
Update on automating reviews
Start doing | Stop doing | Keep doing | Shout outs |
---|---|---|---|
|
|
Action items:
- Lite Farm to write-up script to auto-assign PRs to “Reviewers” team