Habits and routines are useful because they free you to focus on the important tasks. Rituals and processes take a somewhat irrelevant decisions out of your hands, and conventions make it easier for others to understand code and other artifacts. And when you are starting a new approach to work, following the rules by rote can help you understand the method. But circumstances change, and when the reason for the ritual has changed, there are a few possibilities:
- The practice is still useful, for reasons you didn't anticipate when you started it.
- The practice adds less value, but it doesn't add any overhead so there is no harm in continuing.
- The practice leads the team to spend energy addressing a problem that does not exist any more and causes waste.
To avoid instances of the last case that take up too much of you time, it is important to periodically reflect on why you are doing what you are doing, and it it still makes sense in your environment. As your team adopts new tools, new practices, take time to think about whether what you are doing still makes sense. Periodic retrospectives are one way to capture this, so it's important to set aside time to review how you work. (And even to set aside time to review how you do retrospectives!)
Lots of teams (and individual) follow process steps with good intentions, yet they end up causing unnecessary overhead. For example coding conventions that made perfect sense in the days of fixed length variable names, and text editors that add overhead when you have refactoring IDEs and follow clear naming conventions.
The podcast also reminded me of one of of my favorite Gerry Weinberg quotes (which I referenced in Software Configuration Management Patterns):
Traditions and habits have their place. But if you are doing something simply out of habit you can benefit from acknowledging that fact.