Skip to content

v2 Plan and Sprint Notes

Jump to bottom
Dawn Walker edited this page Jan 28, 2025 · 15 revisions

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

Review

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)
    • Nice to have: the data layers move out from under the search results tray

  • Reflections:

    • Haven't yet taken up the testing yet, not sure how to scope timing for that yet
      • Your own sweet spot, maybe after initial PR review
    • Roll our own plugin, need to change styles
    • Used the first PR to get to know the project
    • Secrets (.env file) is easy to be out of sync, no good solution
      • Ideal workflow: catch .env syncing? (obviously not in git, but a .env gen in github for OpenShift token)
      • Om might take on writing this as a script to write, depends on OS, some considerations

Remaining bugs/issues to resolve from this sprint:

  • The base map picker

Planning

Goal: Work on map, focus on high priority features and tasks, especially the radius search functionality

Backlog: https://github.com/orgs/bcgov/projects/171/views/2

Sprint 2 Review and Sprint 3 Planning

Review

Recall, previous goal: Work on map, focus on high priority features and tasks, especially the radius search functionality

PRs:

Planning

Backlog: https://github.com/orgs/bcgov/projects/171/views/2

Goal: faster and smaller PRs.

Moved over from last week:

Sprint 3 Review and Sprint 4 Planning

Review

Recall, previous goal: smaller, faster PRs

Already merged: buttons, contact us page PRs:

  • https://github.com/bcgov/nr-epd-organics-info/pull/366

    • the default behaviour for radius search is that is disappears when you click away
    • question of how to handle what happens when you press "okay" for radius, ability to minimize tray on mobile
    • polygon search "finish shape" operates
    • jamie proposal:
    • DECISION: Final steps
      • carry that active badge (like status)
      • want to grey out okay button once okay locks position, cursor changes back
      • add okay button on mobile to reflect polygon behaviour ("finish shape" locks it)

  • Additional ideas from Jamie:

    • Polygon search if click on first point should close the shape
    • Allow radius and polygon to persist when close the search

  • Did get rid of duplicate Abbotsford, still want to switch to geocoder in backend

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

    • update FN layer name
    • PIDs, they are images, stuck with how it looks

  • Additional ideas from Jamie:

    • convert into vector layer to have more info, to interact with it, etc... (like that beta BC Forestry site)

  • New issues

    • svg link on contact us page not scaling
    • mobile buttons on map

Planning

Backlog: https://github.com/orgs/bcgov/projects/171/views/2

Goal:

Moved over from last week:

Clone this wiki locally