'Ceremonies' and 'Rituals' Won't Make You Agile
Imagine you’ve joined a new company and your new team is using agile. The manager meets you and during the introductory conversation says, “Mondays, we have the planning ceremony at 10 a.m. The other main ceremonies are on Friday afternoons...”
Rewind to where the person said “ceremony.” Did you feel excited? Curious? Nervous? Unenthusiastic?
Words have connotations. For many people, the generic word for these team interactions—“meetings”—carries connotations that are negative. In my experience, using the word “ceremony” (and its close cousin, “ritual”) is worse: It is a signal that your agile implementation is not going to be great. Here is why.
Words communicate hidden assumptions
What people refer to as “ceremonies” and “rituals” are the scrum meetings: the daily standup and the sprint planning, review and retrospective. I hear these words everywhere (searching online for “agile ceremonies” yields 400,000 hits).
Many people who have soured on poorly run “meetings” have opted to use “ceremonies,” because they seem to convey regularity, a set agenda, a strict time-box and clear outcomes. That might be true, but I think they convey additional, subtle assumptions.
Here are some of the assumptions I’ll make—
Please log in or sign up below to read the rest of the article.