(5 votes, average: 3.80 out of 5)
Loading ...If you’ve been watching this blog, then you know that we’ve recently opened the beta registrations for several Windows 7 and Exchange 2010 exams. All of the beta exams that we’ve announced in the past few months have filled at record speeds, and in most cases, we’ve increased the number of beta seats multiple times in order to accommodate your interest and excitement in wanting to participate in the beta process. Because of the Speedy Gonzales nature of these registrations, we’ve had a lot of questions/comments about limiting registrations in a variety of ways (e.g., to just those who hold the previous version of the credential, MCTs only/first, MCPs only/first, invite only, [insert your creative variation here], etc.). So, I thought I’d share a little insight into this process.
We have three major types of beta exams: 1) open (public), 2) invite only (private), and 3) operational. I’ll save the operational beta for a different day because we only use it when we expect very low run rates (niche products or products with slow uptake)—so, it clearly is not part of this conversation.
To get the best psychometric results, a lot of people with a wide range of skills on the technology must take the beta exam. After all, the whole point of a beta is to identify the good items and remove the bad ones. Simply put, I can’t tell if an item can discriminate between high and low performers or if it’s too easy or too hard if the beta sample includes only those who really know (or don’t know) their stuff.
In addition, we want to reach as many people as possible with our certifications, and we want to get people excited about them. When its possible, we try to open the beta exam registrations to as many people as possible who are likely to have the core skill set. For very popular technologies that are largely unchanged from one version to the next, we use an “open” beta because the prevalence and popularity of the previous version of the technology means that most people who register will have some related skills either from the current version (these candidates are highly desired) or from the previous version (less desirable from a psychometric perspective but the reality when you’re dealing with new technology that isn’t commercially available). Open betas allow us to meet both of our goals—psychometric soundness of the beta results and reaching as many people as possible.
For products that are less prevalent with fewer users or with significant changes from one version to the next, we use the “invite only” beta process because I have to be sure that those who take the beta have some passing familiarity with the technology. If I can’t be sure that I will get the sample I need with an “open” beta, the product planners use the “invite only” process. They identify participants using contacts that they have in the industry, product group, and from our SME database. Currently, most of our betas meet our requirements for open betas, but we still do invite only betas for some technologies although it may not seem like it.
So, let’s cut to the chase. How do we ensure that our most loyal candidates—you—have the first shot at registering for a beta exam on a popular technology? Here’s our commitment to you around “open” betas. We will contact SMEs in our SME database who have related skills, indicated their desire to participate in beta exams, and have checked the box at the end of the survey saying that we can contact them FIRST. We will then post the beta code on Born to Learn and associated product specific blogs as appropriate. Remember, though, that seats are limited and registration will always be first come, first served; if you’re interested, register as soon as you see the announcement or invite for a beta. Thanks for your excitement about being part of the exam development process! I love it!
