v2 Plan and Sprint Notes

Capturing our agreements for how we will run Sprints and work together in Jan 2025 as part of the Code With Us Opportunity for v2. This was discussed in our team call and first planning call 2025-01-07.

Sprint cycles

• 1 week sprints
• Schedule additional calls as-needed
• Weekly call: Sprint Review (Demo and feedback) + Planning Tuesday Afternoons
  • For work that requires substantive feedback
  • No separate retros
• During week or after Sprint Review
  • Product Owner and Code Review, approvals on PR

Development practices

• Feature work in a branch
• Open a PR (can use draft mode if needed)
  • when a PR is opened a temporary deployment is created where the changes can be viewed and we can use for demos
• Merge into main requires approvals from others
  • Konane as PO will sign-off on features
  • Code review as needed will be from Om and Aman

---

Sprint Planning

Item	Time (min)
Review sprint format and project tools	0
Set sprint goal	5
Build sprint backlog	20
Consense and Process Check-out	5

Review sprint format and terms

Our plan:

• 1 week sprints (Tuesday to Tuesday)
• 2 meeting formats: Review (30mins), Planning (30mins)

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 (mockups, PO agreement, service design or solution architecting to ensure dependencies have been identified)
• Having a Definition of done for features, typically a checklist covering all work to mark feature as complete

Sprint Review

Discussion of Backlog, work done/not done, and time spent

Sneaking in some Retro: Brainstorm of 2 key questions: what went well in sprint, what could be improved

Demonstrations of sprint work

Outline of key events and/or problems

• Work completed/not completed
• Review Bugs raised
• Identify known and/or descoped issues (if any)

---

Sprint 1

Set sprint goal

• 1-2 sentences, so at future meetings can review to answer "Was this last sprint successful?"
• Get up to speed and familiar with the codebase

Build sprint backlog

• Work from project backlog to develop sprint backlog
• In backlog
  • #231 Map autocomplete
  • #256 Map
  • #257 Map
  • #240 bug on autocomplete results, some exploration
  • #303 some laying out of options for satellite image data

Consense and Process Check-out

• Check in -- this looks okay for now?

• Everyone knows what to do?

• Yes

---

Sprint 1 Review and Sprint 2 Planning

PR: https://github.com/bcgov/nr-epd-organics-info/pull/343

• Question: Should selecting the from the search lead to a "selected state"

  • switch it to select state when a single authorizations was clicked on (not something like a city for example)

• Question: Should we add a new state (selected, filtered, hover state)?

  • let's park this to would be nice to have

• Feedback on base layers:

  • Should be the colour vs. greyscale as default
  • Jamie demo'd hybrid vector / raster approach: https://3d.bcforestengineers.info/#loc=8.52/50.0244/-121.777
    • feedback: this is another nice to have, not want to have right away
  • What we know about users from usability testing: more expert users wanted imagery/additional base layers
  • Replace Pale OSM with topo map
  • staying to visual look in figma (there were updates to BC Design System)

• Reflections:

  • Roll our own plugin, need to change styles

Remaining bugs/issues to resolve:

• the base map picker