Sprint #3 Review and Sprint #4 Planning (2024‐07‐25)

Sprint # Review

Updated the styles on the search page
Updated the button on the details page
Q: how do you clear search by location when you press the location tab? Decision: add feature so when select browser location toggle on/off, if you toggle off, resets the results
Small screen search, was skipped now it works
Added data layers. Noticing with layers:
- needs program area testing of all of them
- two parts: layers + styles need to be defined in call (WMS providers have multiple layers and multiple styles)
Worked on polygon layers and point search today. Still have to work on some testing
- Stretch, if interest: resizable circle that drops as a circle and you can resize just by moving the cursor (Chris demo) <-- would take more time to think thru on mobile
For Konane:
- Results page: name for the file from "export-results-csv"
  - some discussion, will make a ticket to check-in
- Details page: just showing nothing when there is now, any action needed
- program area testing needed of layers, are these all expected behaviour ***
#todo set up time to go through the data layers early next week (with Konane + Dawn)
#todo Om to ask question about crown land boundaries in the Cadastre layers
Out of scope this sprint: link to guidance page from the map layer

Item	Time (min)
Introductions (if needed)
Review sprint format and project tools	5
Set sprint goal	5
Build sprint backlog	30
Consense and Process Check-out	5

Our plan:

Agile approaches:

Sprint backlog a prioritized subset of tasks to work on during the sprint from the full project backlog
~~- User Stories as short, simple description of features from perspective of person wanting system capabilities~~
Identifying a definition of ready for evaluating ability to begin work
Having a Definition of done for features, typically a checklist covering all work to mark feature as complete

1-2 sentences, so at future meetings can review to answer "Was this last sprint successful?"
Guidance page, download documents, and remaining final touches.

can we hide the document section if the API responds with a blank array (which means data not hooked up yet) vs. just no specific docs?
have some more small
Documentation:
- only non-code doc is on the places (wrote the wiki article)
- record design decisions:
  - data layers (translating into leaflet and layers + styles)
  - ... anything else?
- focus on making the code readable first

Yes

#todo: Kunle needs a version of the backlog showing what happened during this code with us, dawn will send a link