Alternatives to agile certificates for delivering quality and value — Ben Linders
I don’t have any agile certificates. As an independent coach, trainer, and consultant, I apply whatever makes sense and looks like a valuable solution in a given context.
In this article, I’ll question the need to be certified in agile, discuss the alternatives, and explain how I deliver quality and value to the people that I work with.
Warning: Explicit Content
This is not a regular “tips and ideas” blog post in which I share my experiences for you to use in your daily work. It’s a personal cry out in which I share my thoughts on a delicate but important topic. If this is not what you like to read then there are hundreds of other articles on my website, so just pick another one and enjoy.
In this article, I’m going against things that are common practice in the software industry, ways of working that a large part of the industry adheres to, supports, and accepts as being the “best and only way to do it”. If your salary depends on this or if you are easily offended then you might want to skip this article.
On the other hand, if you have an opinion on certification, an open mind, and want to learn about my ideas, read on!
Why I don’t have any agile certificates
Nowadays there are tons of agile certificates. I sometimes get the impression that people want to collect as many as possible.
I don’t. I do not have any agile certificates.
So there you have it. I’m not a Certified Scrum Master (CSM), Certified Scrum Product Owner (CSPO) or Certified Scrum Professional (CSP), Professional Scrum Master (PSM) or Professional Scrum Product Owner (PSPO), Agile Certified Professional (PMI-ACP), Certified SAFe® Agilist or Certified SAFe® Program Consultant, or Agile Foundation, Agile Practitioner, or Agile Master.
(BTW, if you want to compare agile certificates, here’s a list of Agile Scrum Certifications).
I’m also not a member of the Agile Alliance, Scrum Alliance, Scrum.org, Agile Consortium, or any other official agile membership organization.
One reason that I’m not certified is that there are simply too many certificates. If I would have to acquire all the certificates that apply to the things that I am capable of, that would take me years doing exams and a lot of money. Time that I rather spend on helping people and money that I prefer to use to live healthy and happily.
Doing exams and spending money on fees to keep certificates alive won’t make me a better trainer, advisor, coach, writer, or presenter. Sure, these certificates and the badges that come along look nice in presentations, on LinkedIn, and when you’re at conferences. They will probably also help to impress (potential) customers.
But they don’t increase the value that I deliver, which is what matters most to me, and to the people that I work with.
What I see a lot is that people who are certified in a specific method, framework, or approach tend to think that there are no other solutions. It’s the classic “if all you have is a hammer, everything looks like a nail” approach. Which often comes with “my hammer is bigger, better, faster, and cheaper than yours”.
I don’t believe that’s true, and I don’t want to work that way.
I’m independent for a good reason: I don’t want to restrict myself in any way and be able to apply whatever makes sense and looks like a valuable solution in a given context. This is also why I signed the Oath of Non-Allegiance:
I promise not to exclude from consideration any idea based on its source, but to consider ideas across schools and heritages in order to find the ones that best suit the current situation.
Jerry Weinberg inspired me to think about problems and come up with multiple solutions. He stated: “If you haven’t thought of three possibilities, you haven’t thought enough.” Being independent allows me to come up with many solutions and pick the most suitable ones.
Educated and experienced
Does not having agile certificates mean that I did not get any proper education? On the contrary, I got a lot of education during my life (my grey hairs are the living proof of this), and I’m a lifelong learner.
I do have a technical bachelor degree and there’s a long list of Master modules that I have done which includes psychology, sociology, culture, communication, organizational change, marketing, and business IT alignment.
The ways that I learn most (in no specific order) are:
- Joining conferences, meetups, online forums, and open spaces.
- Interact on social media: Ask questions and respond, have discussions.
- Interviewing people and researching for InfoQ.
- Advising, coaching, and training people.
I also learn a lot by thinking about stuff, researching it, and writing it down (which is one of the reasons why I’m blogging and writing books). I use the things that I learned when I teach, write, advice, coach, and present. And when I do that, I ask for feedback to further improve myself.
If you want to know how I started with agile, read the story of how my team and I collaborated with our customer on my first project, doing agile when the Agile Manifesto wasn’t invented yet, to deliver high-quality software.
I’m also a former affiliate of the Software Engineering Institute at Carnegie Mellon University where I investigated factors that drive software quality. So I know how to prove and disprove things.
Alternatives for agile certificates
If you are looking for a professional, of course it’s easy to make a list of the required certificates and then take a checklist approach to tick them off. But how much does that tell you about what a person really can do and how they will match and be valuable for you and your organization?
There are alternatives to selecting a consultant, coach, or trainer, not basing your decision on the certificates that they have. I’m convinced that in many situations this will even work better.
Some of the alternatives for agile certification are:
- Browse through their blog to see what someone writes about and how they share their experience. Look at the comments on their posts and see how they react.
- Check their LinkedIn profile to see what they have accomplished, where, when, how, and with whom.
- Don’t forget to read the recommendations. They tell a lot about *how* people accomplish results (which is something a certificate doesn’t show).
- See how someone behaves on social media. Do they suggest solutions to problems? Refer to existing solutions and give credit? Act respectfully?
- Check your network to see if someone you respect knows the person and can tell you about him/her. Personal anecdotes about behavior and beliefs tell a lot.
- See what books have been published by someone and how these books have been received by their readers.
- Google the person, see what shows up and think about how that could help you to solve the problems that are keeping you awake at night.
- Find out how someone reacts when they made a mistake. Do they admit it, are they open and honest? Have they learned something?
- Reach out, ask a question, and see how someone respond. Do they offer help, or do they negotiate and want to sign a contract (the manifesto for Agile Software Development call this “Customer collaboration over contract negotiation”).
- Create your own certificate. Although not something that can help to select the right person, creating some kind of “certificate” can be a great way to celebrate and have some fun together.
These are things that certificates don’t tell you. They can make a huge difference!
Certificates don’t deliver value. Value is delivered by people who have experience and dare to do things!
Value comes from someone who truly tries to understand your problems and provide more than one solution that might work. Who experiments, verifies, learn, and improves.
If you want someone who will force their favorite agile framework or method in which they are certified in on everyone in your organization, go ahead and search for consultants with certificates.
If you are looking for someone who knows about true agility to deliver quality and value, let’s talk!
Originally published at https://www.benlinders.com on August 29, 2018.