generated from bcgov/quickstart-openshift
-
Notifications
You must be signed in to change notification settings - Fork 1
[Template] Sprint Planning, Review, and Retros
Dawn Walker edited this page Jan 8, 2025
·
5 revisions
Sneaking in some Retro: Brainstorm of 2 key questions: what went well in sprint, what could be improved
- Work completed/not completed
- Review Bugs raised
- Identify known and/or descoped issues (if any)
| Item | Time (min) |
|---|---|
| Review sprint format and project tools | 0 |
| Set sprint goal | 5 |
| Build sprint backlog | 20 |
| Consense and Process Check-out | 5 |
Our plan:
- 1 week sprints (Thursday to Thursday)
- 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
- 1-2 sentences, so at future meetings can review to answer "Was this last sprint successful?"
- Work from project backlog to develop sprint backlog
- Check in -- this looks okay for now?
- Everyone knows what to do?