Ask HN: Do you have refinement sessions too?
My team has one (sometimes two) refinement sessions per sprint (1 sprint = 2 weeks). What we do in these sessions is basically a mini-brainstorming about jira tasks that will go into the next sprint (plus assigning story points). Typically one engineer is on charge of presenting a jira task for refinement (usually a jira task is written by a product manager, but there are gaps and the assigned engineer needs to “fill the gaps” so that the whole team knows what the task is about).
We just got a new manager (ex faang), and he has introduced refinements in our sprints. I can’t but think these refinement sessions are huge waste of time.
3 comments
[ 3.8 ms ] story [ 17.9 ms ] threadPointing stories and thinking about what goes into the next sprint doesn’t sound like refinement to me. That sounds like a sprint planning.
So, now we just send a sacrificial engineer to do refinement, usually picked by whomever did the fewest code reviews since the last refinement. It's actually worked too well. I get code reviews in 10 minutes instead of hours.