Sabrina Ferlisi As a Scrum Master, I notice that Scrum is becoming more and more democratic which, from my point of view, is a good thing. Companies are realizing that what worked 40 years ago is no longer applicable in today’s world and that a change is necessary.
These new Scrum practices are sometimes based on the experience of colleagues or on articles read on the Internet. I notice that few people take the time to go back to the source and read the Scrum Guide, a 13-page booklet that as its name indicates contains the rules of the game of Scrum. As a result, Scrum is applied without necessarily understanding the purpose behind certain events or certain responsibilities of the Scrum team (such as the Scrum Master’s responsibility to make Scrum understood and respected).
It is in this context that I imagined writing this series of articles on Scrum events to re-explain the fundamentals around the events, to present the improvements related to the new version of the Scrum Guide released in November 2020 and to debunk some myths around Scrum.
