Sprint planning - S109
@Link to the recording:
Passcode: *6efwm5m
Themes and priorities for this sprint:
Highest Core Team Priorities
Sensors: https://lite-farm.atlassian.net/browse/LF-4684
https://lite-farm.atlassian.net/browse/LF-4686
Work-in-Progress
https://lite-farm.atlassian.net/browse/LF-4688
Work-in-Progress
Pivots and Irrigation Prescriptions: https://lite-farm.atlassian.net/browse/LF-4759
Work has begun on https://lite-farm.atlassian.net/browse/LF-4760
Backup scope (secondary priority)
Allow modifying completed tasks: https://lite-farm.atlassian.net/browse/LF-4737
@Loic Sans to create designs for a “re-complete” flow that triggers only the completion screens
Backup backup scope (third priority)
No email on consent: https://lite-farm.atlassian.net/browse/LF-360
For scope confirmation
Allow modifying completed crop plans: https://lite-farm.atlassian.net/browse/LF-4736
Highest Contributor Priorities
*Please tag dev or design on ticket if requirements are not clear or defined
IN PROGRESS (TECH DEBT)
AVAILABLE BUGS
Highest priority
Medium priority
(Sizeable task, relating to persisted form data across app) https://lite-farm.atlassian.net/browse/LF-4614
Lower priority
Reading for this sprint
Intro reads:
Getting started! [10 minutes]
Tips and tricks [5 minutes]
Intro to the LiteFarm app [20 minutes /w videos]
A brief tour of the codebase and tech stack [5 minutes]
Source control and the developer’s workflow [5 minutes]
Smart Irrigation specific reads:
Other readings haven’t been significantly updated since S79. However, they’re listed below from most high level to most detailed:
https://lite-farm.atlassian.net/wiki/spaces/LITEFARM/pages/1483472927 -[2min]
https://lite-farm.atlassian.net/wiki/spaces/LITEFARM/pages/1694629889 - [9min]
https://lite-farm.atlassian.net/wiki/spaces/LITEFARM/pages/1185611781 - [7min]
https://lite-farm.atlassian.net/wiki/spaces/LITEFARM/pages/1202290689 -[6min]
https://lite-farm.atlassian.net/wiki/spaces/LITEFARM/pages/1732935690 - [6min]
Forward-looking reads:
What’s the definition of done for a story?
Code
Note update language requirements:
Add string to
en
Mark your PR with the “new translations” tag
The CrowdIn GitHub automations will do the rest
Unit testing
Check in with @Loic Sans if there’s a visual component to the story
Open up a PR, and leave it unassigned. Two reviewers from the core team will be automatically added. Core team to incorporate feedback given during peer review.
Passes peer review x 2
Reviewer will be auto-added
Merged
Passes verification
User stories with UX/UI component: Passes validation with @Loic Sans
Modifications to the
Team availability
S108 runs from … to …
Thursday, March 27th | Wednesday, April 9th |
Days in sprint: 10
Person | Days in sprint | Notes |
@Sayaka Ono | 10 |
|
@Joyce Sato-Reinhold | 10 |
|
@Duncan Brain |
|
|
@Denis Dovganyuk | 10 |
|
@Loic Sans | 10 | Apr. 9th will have different hours |
@Larisse Cavalcante | 3 | limited availability until Apr. 7th |
@Divya Chayanam | 10 |
|
@Anto Sgarlatta | 10 |
|
Contributors |
|
|
|
|
|