GASP: Backlog Grooming Meeting
Many are surprised when I tell them that not every Scrum team has such a meeting each sprint
From what I’ve see, if backlog grooming doesn’t occur prior to a sprint planning meeting, the the planning meeting with be “painful“. So if you don’t groom the backlog, consider doing so soon. This leads us nice to DEEP:
- Detailed Appropriately. User stories on the product backlog that will be done soon need to be sufficiently well understood that they can be completed in the coming sprint. Stories that will not be developed for awhile should be described with less detail.
- Estimated. The product backlog is more than a list of all work to be done; it is also a useful planning tool. Because items further down the backlog are not as well understood (yet), the estimates associated with them will be less precise than estimates given items at the top.
- Emergent. A product backlog is not static. It will change over time. As more is learned, user stories on the product backlog will be added, removed, or reprioritized.
- Prioritized. The product backlog should be sorted with the most valuable items at the top and the least valuable at the bottom. By always working in priority order, the team is able to maximize the value of the product or system being developed.