/
Backlog Grooming
Backlog Grooming
Backlog Grooming (aka Backlog Refinement)
Lead: Mary Jo Kochendorfer (Deactivated) and/or Team Leads
Product Owner, Team Leads + chosen team members, Scrum Master(s)
No more than 2 hours
Objective: Review the high-priority tickets and/or discuss what the next sprint should focus on. The product owner will highlight the functional priorities and the tech leads will highlight the technical priorities.
When:
Team VR:
Team JSI:
Team Ona:
Team Parrot:
Meeting Invite: OpenLMIS v3 Backlog Grooming.ics
Process Details:
- Backlog grooming is most likely to succeed when the following have been accomplished prior to the meeting:
- The Product Owner has defined the functional priorities for each team for the next sprint. These are marked in bold within the particular team's section.
- The team has created tickets in Jira with sufficient detail that relate to each functional priority.
- The team lead has curated these tickets and linked to them in the "Backlog Grooming Sprint NN" page each ticket should have a checkbox next to it
- During the meeting:
- Product Owner outlines functional priorities and the team discusses any conversations that are jotted down per functional area
- Review each ticket that is proposed by functional area
- Determine if the ticket is scoped well enough and if there are any dependencies that aren't accounted for
- Develop a roadmap of gaps that need to be completed in the backlog before the next sprint can start
- The team prepares for the Planning meeting where story points and estimates are defined.
Backlog Grooming Page Sample
This section displays a subset of the backlog that was completed for Sprint 47:
Vaccine Stock Based Requisitions
- A:
-
OLMIS-4055Getting issue details...
STATUS
(MUST)
- - OLMIS-4016Getting issue details... STATUS (MUST)
- Q:
-
OLMIS-3916Getting issue details...
STATUS
(MUST)
Fulfillment
- Q: - OLMIS-4077Getting issue details... STATUS (MUST)
- - OLMIS-3826Getting issue details... STATUS (MUST)
-
-
OLMIS-2734Getting issue details...
STATUS
- Fulfillment current Integration Test approach slows developers down
Items to note:
- Each functional area is in bold
- Each ticket has a checkbox next to it representing a task
- One item without a checkmark means that this ticket was considered, but not picked up by the team.
- The priority defined by the Product Owner is in parenthesis (MUST) to signal to the team leader that this is critical.
- The "Q:" signals to the Product Owner that this issue has a question that needs to be addressed before the sprint beings.
- The "A:" signals to the Team lead that the Product Owner has responded in the ticket.
Meeting Notes
- Archived Backlog Grooming Pages
- Template - Backlog Grooming Sprint 1NN
- Backlog Grooming Sprint 140
- Backlog Grooming Sprint 141
- Backlog Grooming Sprint 142
- Backlog Grooming Sprint 143
- Backlog Grooming Sprint 144
- Backlog Grooming Sprint 145
- Backlog Grooming Sprint 146
- Backlog Grooming Sprint 147
- Backlog Grooming Sprint 148
- Backlog Grooming Sprint 149
- Backlog Grooming Sprint 150
- Backlog Grooming Sprint 151
- Backlog Grooming Sprint 152
- Backlog Grooming Sprint 153
- Backlog Grooming Sprint 154
- Backlog Grooming Sprint 156
- Backlog Grooming Sprint 157
- Backlog Grooming Sprint 160
- Backlog Grooming Sprint 161
- Backlog Grooming Sprint 164
- Backlog Grooming Sprint 165
- Backlog Grooming Sprint 166
- Backlog Grooming Sprint 167
- Backlog Grooming Sprint 168
- Backlog Grooming Sprint 173
- Backlog Grooming for Sprint 175
- Backlog Grooming for Sprint 176
- Backlog Grooming for Sprint 177
- Backlog Grooming for Sprint 178
- Backlog Grooming for Sprint 179
- Backlog Grooming for Sprint 180
- Backlog Grooming for Sprint 181
- Backlog Grooming for Sprint 182
- Backlog Grooming for Sprint 185
- Backlog Grooming for Sprint 186
- Backlog Grooming for Sprint 187
- Backlog Grooming for Sprint 188
- Backlog Grooming for Sprint 189
- Backlog Grooming for Sprint 190
- Backlog Grooming for Sprint 191
- Backlog Grooming for Sprint 192
, multiple selections available,
Related content
Project task report blueprint
Project task report blueprint
Read with this
Version 3.4 (2018 May - August)
Version 3.4 (2018 May - August)
Read with this
Living Product Roadmap
Living Product Roadmap
Read with this
Testing Templates
Testing Templates
Read with this
Functional Specification Template
Functional Specification Template
Read with this
The 3.19 Regression and Release Candidate Test Plan
The 3.19 Regression and Release Candidate Test Plan
More like this
OpenLMIS: the global initiative for powerful LMIS software