A stakeholder asks the Scrum Master, 'when exactly is your team's refinement meeting, so I can send my request in time?' The Scrum Master explains there isn't a single fixed slot the way there is for the Daily Scrum. Why is that answer accurate under the 2020 Scrum Guide?
Select an answer to reveal the explanation.
Short Explanation
There's no clock to catch here — refinement isn't pinned to a slot the way the Daily Scrum is pinned to 15 minutes at the same time each day. The Scrum Team refines whenever it's useful, so 'send it in time for the meeting' isn't really a thing.
Full Explanation
The 2020 Scrum Guide describes refinement as an ongoing activity in which the Product Owner and Developers add detail, estimates, and order to Product Backlog items, and it explicitly gives the Scrum Team latitude over how much time to spend on it and when. That's a real structural difference from the Daily Scrum, which is a formal event with a fixed 15-minute timebox held on the same cadence every working day of the Sprint. Telling a stakeholder there's no single fixed refinement slot is accurate, and it also sets an honest expectation: the right move for a request is routing it to the Product Owner whenever it's ready, not timing it to a meeting that may not exist in a fixed form. The claim that refinement was removed from Scrum entirely is false — it's still named in the Guide, just without event status; the claim that it happens only once, in the first Sprint, misunderstands it as ongoing across the product's life, since new information keeps surfacing, such as a certification requirement changing or a parts supplier shifting, that items need re-refining against. And it isn't purely individual, either — while any Developer can refine solo, it commonly involves the Product Owner and other Developers together. A concrete check: can the Scrum Team point to refinement happening more than once across a Sprint, at times that varied?