What's wrong with calling Scrum events "Ceremonies?"

In this episode, Professional Scrum Trainer Eric Landes addresses the questions: "hy would the Scrum guide not use ceremonies and events interchangeably?"

Introduction

In some classes, students will refer to the scrum events as ceremonies.  Yet the guide refers to these as events.  So why would the Scrum guide not use ceremonies and events interchangeably?  My answer typically is something along these lines:

What is a Ceremony?

While we might be able to use these words interchangeably, I think there is a reason for the distinction.  There is not a clear explanation in the scrum guide why this is.  But if we look at the definition of “Ceremony,” we might find some hints.  According to dictionary.com, one of the definitions of ceremony is "the formal activities conducted on some solemn or important public or state occasion".  I think the key is in formal and solemn.  In fact, most of the rest of the explanations include the word or a variant of the word formal.

What is an Event?

In contrast, dicitonary.com defines event.  "something that happens or is regarded as happening; an occurrence, especially one of some importance."  The scrum guide says this about events - "Prescribed events are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum.” The talk of creating regularity is better defined by event than ceremony to me.  And this speaks to scrum as a whole.  It is more about a framework that helps solve complex problems, it's not a solemn process that teams must follow.

Scrum Should Minimize Other Meetings

I also emphasize to students that the events are supposed to minimize the need for meetings not defined in Scrum.  If team members are saying that Scrum makes most of their time about meetings, I will respond that this is not from the scrum framework.  This may be an issue where prior meetings for non-scrum frameworks are still on the books and may not be necessary!  As a team take some time and evaluate the need for these meetings.

Collaboration is Key

Sometimes I will tell classes that Scrum and other agile frameworks were invented to make sure that developers meet in a regular cadence.  Collaboration was not a necessary component of software development when I first started.  Agile frameworks just showed us knowledge workers how much we needed collaboration and gave us events that made sure we were collaborating! 

Conclusion

So whatever we call these events, make sure to follow the framework, and use them to encourage and foster team collaboration!

Want to Learn More or Get in Touch?

Register for our upcoming web meetings by visiting agilethought.com/events

See available training courses at agilethought.com/training.

Visit the website and catch up with all the episodes at AgileThought.com!

Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!