Certification schemes vary massively. Professionals and organisations have a hard time deciding whether they are trustworthy indications of quality or a futile box-ticking exercise.
A certificate can be an indication that the bearer has sat in a training room for a day or compelling evidence that they have deep knowledge and broad experience. It seems obvious that the former are not as valuable as the latter, but you wouldn’t guess this by reading through a pile of job specifications. The requirement to hold a certificate, if mentioned at all, is often for certificates at the cheaper, easier, less meaningful end of the spectrum.
This session follows my struggle with the certification process as I sought to create one for my own company. We’ll look at the various sorts of agile certification available and explore the reactions they have elicited from practitioners and employers. From this we’ll build an understanding of the various goals and challenges that any certification scheme will face. And you’ll see how I reached a compromise that will hopefully work for my company, our customers, and our associates.
You’ll leave with enough information to allow you to make a value judgement about some of the well-known Agile certification schemes that exist, how to determine whether you should trust them, and what their existence bodes for the future of the Agile eco-system.