dmoore44 wrote: » I just started a class on Enterprise Architecture as part of my grad program, and on the second slide of the intro deck, there's this remark from the professor: "EA is business focused but IT aware; it is strategic first – then tactical". The first lecture then went on to provide these nuggets of information: EA expectations • Optimize, across the enterprise, the often fragmented legacy of manual and automated processes • RE-position the IT environment such that it is responsive to change and supportive of the business strategy • Effective management and exploitation of information through IT capability • Provide a strategic context for the evolution of IT systems in response to constantly changing needs of the business environment • Bridge the gap between Business and IT With that, I think it might be worth it to clarify your desires... If you want to be an Enterprise Architect, then TOGAF/FEA/Zachman are going to be your frameworks of choice, and you'll need to be as knowledgeable of business concepts as your are of IT concepts. The focus here is more on strategy and how IT/IS can be leveraged in to competitive advantage. If you're looking for a more technically inclined role that takes advantage of the MCSA/MCSE-type certs, then you're looking for an IT architect role. Here, you'll be in charge of implementing the systems that EA dreams up to advance some capability that the business desires. The aforementioned focus here is on implementation and is a more tactical role.
slinuxuzer wrote: » I would really do some deep thinking and research on this if I were you, and ask why do I want XYZ title. There are many different grades of "Architect" New Business architects or sales architects range from roles that do pre-sales technical briefs and high level planning, all the way to guys that do detailed RFP response, specifically the latter takes place a lot in public sector. As others mentioned some roles are more technical and others are more business centric, a role sort of like mine that would be called "Chief Archiect" or managing principal has a good mix of business and technical, I manage a team of technical principals, so I do a little of both, maybe 75% management and 25% tech. TOGAF is something I see around a lot, no one mentioned it, but I will VMware VCDX is a design level cert, albeit vendor specific, maybe worth doing a little research on. Cisco also has a design cert. maybe those are options if you are wanting to stay technical.
stryder144 wrote: » It might help to get CAPM/PMP to add to the list of future certifications.
DatabaseHead wrote: » Sorry for coming off sounding brash, but why would you get a PM cert when you want to be a enterprise architect, or solutions or integration etc....... (Architect). Get the TOGAF or SOA and call it a day. There are several reasons this is the right play. Terminology alone, when crafting your resume and explaining your task / role you'll pick up on dialog provided from these methodology/frameworks. This alone will help you out exponentially when it comes to securing the position. It will also help you fill in the gaps as you become more aware of what you don't know you don't know. How in the Sam Hill is a PM certification going to help with your effort?
Azt7 wrote: » I agree that it is not related directly. However looking at some job postings, they require PMP sometimes. I guess it is more of a way to filter candidates.
DatabaseHead wrote: » Well heck I've seen an architect job once requiring A+, you might as well pick that baby up as well!!!
DatabaseHead wrote: » Smart move going for SOA. Which one are you going for, Architect? (I hope)
beads wrote: » Does the title matter that much? Currently, I work up and down the entire stack as a CSO but my title lacks the 'O'. Still I get paid more than the average 'O' level executive? In the end I never got to hung up on titles and just refer to myself as 'security', skipping the pretentious professional titles used by professional (licensing) organizations like Engineer or Architects. We are analysts and technicians but understand their is no good language for what we do today. File under title inflation. - b/eads
DatabaseHead wrote: » Unfortunately that's just not real world. Your title is your brand or at least part of it so it most certainly does matter. While an over inflated title, such as director of desktop support is about as stupid as it comes, so does an TRUE architect called a Business Analyst...... Nothing pretentious about right sizing your title to your daily duties. In fact it's called being smart......
Azt7 wrote: » Definitely agree with your point. I always found funny how there's what a job title / description is and then there is what the day to day really is. And there's a salary gap too which I'm not even going to go into. It's one of the reasons why I'm definitely requesting a promotion this fall to have the full-fledge proper title to match what I actually do on a daily basis.
UnixGuy wrote: » Get some Azure/AWS cloud architect certs
Azt7 wrote: » Is it weird to have both Azure and AWS certs ?