generated from bcgov/quickstart-openshift
-
Notifications
You must be signed in to change notification settings - Fork 1
v1 Sprint 1 Planning (2024‐07‐05)
Dawn Walker edited this page Jan 3, 2025
·
1 revision
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:
- 1 week sprints (Thursday to Thursday)
- 2 meeting formats: Review (30mins), Planning (45mins)
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?"
Get a basic map view up that displays markers for facilities (markers, zoom in/out, headers from auth page). Complete onboarding to materials: review figma, get answers to any questions.
- Work from project backlog to develop sprint backlog
- Already: reviewed the figma and decomposed things into smaller pieces, have an initial sense of high-medium-low priorities.
- Next: seeing search input as a big piece, lowest: custom searches, polygon or circle, want sense priority for data layers
- Konane: those data layers are important because of regulatory context, lower priority okay, but want at the end
- Check in -- this looks okay for now?
- Yes
- Everyone knows what to do?
- Yes
- Action Item:
- Chris to take a first pass of moving items on the backlog into all sprints + decomposing and creating new issues this week
- Chris to email Dawn UX/design questions from figma