The Scrum Guide talks about “events”. This is not an attempt at being elitist or at making things unnecessarily vague. I think that the choice of the word “event” has the purpose of leaving the implementation open, allowing us to channel the empiricism characteristic of Scrum towards evolving the event into a met…
Erik de Bos
Oh, nice. It never occurred to me that the reason for calling it event might be that it’s not prescribed to be a meeting.
Noteworthy, though, that the refinement itself is not even described as an event. The Scrum guide describes it as an on-going process. Which makes sense because even with the typical implementation of a refinement meeting, it still makes sense to add details at any time, new insights arise.