Microsoft Certified Architect

I was reading David Ing's blog and came across an entry talking about what it takes to be a software architect.

Microsoft has also found interest in trying to qualify these individuals and has come up with its list of competencies as follows: (for those who are too lazy to click on the link or want a quick summary keep reading)

• Leadership: Candidates demonstrate that they develop partnerships with stakeholders across the organization on their projects; that they can mentor others; that they develop and form strong teams; and that they achieve successful results.
• Technology Depth: Candidates demonstrate that they have a deep understanding of the concepts and application of at least two core technologies (for example, messaging, storage, Windows, networks, etc.) plus the ability to quickly assimilate information about new technologies.
• Technology Breadth: Candidates understand architectural best practices and are able to apply them across a breadth of technologies to orchestrate a solution. They also have views on the future development of a technology and how it might influence current solutions. Finally, they understand the interaction between infrastructure, solution, and enterprise architecture and practices.
• Strategy: Candidates demonstrate understanding of enterprise architectural frameworks such as TOGAF and operational frameworks such as ITIL and be able to use these frameworks in their projects. They also understand project management principals and how architects interact with project managers to deliver projects. In addition, they understand the economic dimension of projects and how costs influence the available choices for technology.
• Organization Dynamics: Candidates show that they are able to recognize the key stakeholders in a project and that they can work with those stakeholders to drive a project to a successful conclusion. They present the ability to pick the right battles at the right time and then recognize the political landscape that influences a project within an organization and then influence organizational politics for the success of their projects.
• Tactical/Process: Candidates demonstrate that they can gather and refine project requirements from both a technical and business perspective. They understand how to effectively prototype and test a solution and also showcase the talent to create effective project artifacts. Lastly, they exhibit the ability to refine project goals and the tactics necessary to achieve those goals as the project develops.
• Communication: Candidates show that they maintain well-written and accurate project documentation; they are able to present information on a technical subject in a concise and measured manner; they have the ability to influence others; they have the ability to manage conflicts effectively; and to tailor their communication to the needs of the target audience.

So for pioneering individuals wishing to relate to the architecture community or more specifically would like to become an architect, the above highlights some of the skills required.

FYI the program is very saturated with requests at the moment and once they weed through the applicants to produce candidates they'll be accepting more of the former.If, by chance, you are lucky enough to get into the program expect a very grueling board awaiting to see if you truly have the “right stuff”. <Paper Certification individuals need not apply>