In the world of Agile, one ghost that haunts us is dogma. If you’ve been in Agile long enough, you’ve probably encountered those dogmatic individuals who cling to a rigid set of beliefs, refusing to adapt or consider the actual data, feedback, or experiences of the people around them. These folks? They need to be shown the door 🚪. Agile is about flexibility, adaptation, and collaboration—dogma has no place here.
Pragmatism vs Dogmatism in Agile
Let’s get one thing straight: while I strive to be pragmatic almost 100% of the time when working with teams, there are times when I can get a bit pedantic. And that’s usually in a training environment, where precision and clarity matter. If I’m teaching Scrum, Continuous Delivery, or any other framework or technology, I will be very specific about terminology—what things are called, why they are called that, and how they interact with other elements.
Why? Because it’s essential to understand the language and the principles behind what we’re learning. Whether you’re learning Scrum or mastering C#, the words we use and the definitions matter. But that precision shouldn’t bleed into dogma when we’re back in the real world working with teams. This is where we need to shift from pedantry to pragmatism.
Real-World Example: A Fired Scrum Master
Let me share a story to highlight the importance of being pragmatic. A good friend and mentor of mine, Stephen Borg, once told me about a Scrum Master who got fired. Now, it’s not often you hear about Scrum Masters being let go, but in this case, the reason was their rigid, dogmatic approach.
This Scrum Master insisted that the team must stand during the daily stand-up meeting—after all, it’s called a “stand-up,” right? But here’s the kicker: the team had a disabled member in a wheelchair. To ensure everyone was on equal footing, the team decided to sit during the stand-up. This was an act of respect and inclusion, which is fundamental to Agile. They were prioritizing openness, respect, and courage, the very values we hold dear in Scrum.
However, this Scrum Master didn’t see it that way. To them, the rule was clear: stand during the stand-up or you’re not doing Scrum. The result? They were fired for their inflexibility, for sticking to a dogmatic interpretation of Scrum that overlooked the true essence of Agile: adapting to the needs of the team.
Key Takeaway:
- Being dogmatic about processes can do more harm than good.
- Flexibility is crucial in creating inclusive, respectful environments.
- Agile is about the people, not just the processes. 👥
The Importance of Flexibility in Agile
This brings us to the heart of the matter—why dogma can be so damaging in Agile. Dogma is rooted in blind belief, in adhering to a set of principles or rules regardless of the evidence to the contrary. Agile, on the other hand, thrives on continuous learning, experimentation, and iteration. In the example above, the team demonstrated true agility by adapting their process to better suit the needs of the individuals involved. Sitting down didn’t make them any less Agile; in fact, it showed their commitment to the values that define Scrum.
If you’re not adapting, you’re not Agile. If you’re following rules just for the sake of following them—without understanding their purpose—you’re missing the point. And that’s where dogma rears its ugly head.
Why Flexibility Matters:
- Agile is all about responding to change and adapting to new information 📈.
- Dogmatic approaches stifle innovation and progress.
- Teams thrive when they have the autonomy to adjust processes based on their specific context.
Pedantic vs Pragmatic Approaches
Now, let’s be clear: there’s a difference between being pedantic and being dogmatic. As I mentioned earlier, being pedantic—focusing on the precise meaning of terms and frameworks—has its place, particularly in training. It’s crucial to ensure that everyone is speaking the same language and that concepts are clearly understood.
However, when it comes to working with teams in the real world, pragmatism should always win out. Every team is different, with its own set of skills, experiences, and challenges. Being a good Scrum Master or Agile coach means working within the context of the team, understanding their unique needs, and adapting accordingly. It’s about being flexible and open, not rigid and dogmatic.
Pragmatic Approaches in Agile:
- Meet teams where they are, not where you think they should be.
- Focus on outcomes and value delivery, not strict adherence to rules 🛠️.
- Encourage open dialogue and experimentation to find what works best.
Overcoming the Ghosts of Agile Past
If you’re being haunted by the ghosts of Agile past—whether it’s dogma, outdated practices, or rigid mindsets—it’s time to let go. Agile is about delivering value, continuously improving, and responding to feedback. Holding on to dogmatic principles that no longer serve the team or the product will only slow you down.
As we’ve seen, dogma can undermine the effectiveness of a team and stifle its ability to deliver value. The longer it lingers, the more damage it can do. So, if you’re struggling with these Agile ghosts, it’s time to exorcise them. Whether you need a coach, a consultant, or just some advice, don’t hesitate to reach out.
Conclusion: Embrace Pragmatism, Reject Dogma
In Agile, we need to focus on pragmatism over dogmatism. Teams are made up of individuals with diverse backgrounds, skills, and experiences, and no single approach will work for everyone. Agile is about adaptability and finding the best path forward for your team, not rigidly following a set of rules.
So, if you find yourself or your team stuck in dogmatic thinking, remember this: it’s not about the rules; it’s about delivering value and improving continuously. Don’t let the ghost of dogma haunt your Agile practice 👻. If you want to discuss your unique needs or situation, book a call or visit us at nakedagility.com. We’re here to help you clear the path to better agility, free from the specter of dogma.