It's not rare in my experience. It's basically a bunch of experienced engineers getting together for a weekend warning inexperienced engineers about newbie mis

It's not rare in my experience. It's basically a bunch of experienced engineers getting together for a weekend warning inexperienced engineers about newbie mistakes, like obsessing too much about new shiny tools / frameworks / processes created by people from the past, or leaving mess behind. At Google we were doing mostly agile actually (didn't really have any complex process, but had quarterly goals to check ourselfs and get feedback, also weekly check if we are going in the right direction). ,,this week'' snippets about what we're going to do this week. All light stuff to make sure that it doesn't hinder real coding work. Cross team work was much more messy of course, but inside teams this worked fine. At another small company I worked it was almost the same, we just didn't call it agile.