If you asked me 12 months ago what an ALM MVP was I would likely have told you something – unfortunately that something would have been completely wrong. One of the most important things I learnt this year from being an ALM MVP, is what an ALM MVP actually is.
First it is an award, this means you get it as recognition for doing something which benefits the community of people who use a Microsoft product (or products). It is also very important to note that the reason it is awarded to one person is seldom it is awarded to another person – no two people are alike, neither are their community contributions and so the awarding is unique per person.
I think it is safe to assume that if you going to so something which benefits many people using a specific product, you need to know something about that product However being a MVP is not meant to indicate that this person is an expert in a certain product/s and they know everything about the product.
This doesn’t mean that a lot of MVP’s aren’t brilliant, many are scary smart, first two that jump to mind are Ed Blankenship ALM MVP and Jon Skeet C# MVP, but at the end of that day – all MVPs are people, like you, with limits and gaps in knowledge.
ALM MVP’s have an additional level of complexity since the community that they helped revolves around not one single product, like Zune MVP’s for instance, but is actually made up of many products and components. Above is the “stadium” picture which shows a lot of (most of?) the components which make up ALM.
A ALM MVP may know and work in one product/component and never see the other ones. An example of this is Zayd Kara ALM MVP, who is deeply IT Pro focused – so he understands installing the systems, build in TFS etc.. but he seldom opens or works in the Visual Studio IDE so he may not know as much about it as a other ALM MVPs.
As I stated above the reasons someone is awarded differ and so the area and skills in the ALM MVPs differ from person to person.
In the form of a Q&A:
Yes, I am a fan of Microsoft tools but I am also critical of them. You want to see some of the most critical people of Microsoft is MVP’s – they care and fight on behalf the community. As most (all?) MVP’s we are matured to realise that these are just tools and you need to pick the right tool for the job, and that sometimes isn’t what Microsoft currently offers.
Also worth thinking about, is that Microsoft wants the best of the best (which company doesn’t?), MVP’s are awarded for their community work – not being the best of the best C# programmer (for example) so sometimes that means that MVP’s are not the best fit and the final thing weighing against you (as told to me by a Microsoft employee)
Most of the Microsoft employees do not even know of or understand the MVPs so there is not a lot of help in their.
However being a MVP means you are likely following key people so when exciting jobs are announced ,like the way I knew about these cool jobs, you are first in with your CV.
First there is no single way to becoming a MVP – the IW user group leads are a good example of that we have a few MVP’s but we have more non-MVP’s as leads. Second if your motivation of helping the community is to become a MVP, then I doubt you will become a MVP because your motives are wrong. MVP’s do what they do for the community not because they want to be a MVP, but because they love the community.
To make sure I wasn’t still wrong, I did ask for some feedback from fellow MVP’s and Microsoft staff and I thank you all for your contributions in particular Willy-Peter Schaub, Ruari Plint and Zayd Kara.