Skip to main content

skip to main content

developerWorks  >  Architecture  >

Enterprise IT architect: Meet the new kid on the block

Understanding and assuming the role of the enterprise IT architect

developerWorks
Document options

Document options requiring JavaScript are not displayed

Discuss


Rate this page

Help us improve this content


Level: Introductory

Danielle Ruest (architectures@reso-net.com), Senior IT Enterprise Architect (EITA), Resolutions Enterprises
Nelson Ruest (architectures@reso-net.com), Senior IT Enterprise Architect (EITA), Resolutions Enterprises

09 May 2006

A new role is developing in IT shops around the world: the enterprise IT architect. Discover why this role is critical for your software development team, and your entire organization, to move forward. Learn which skill sets are required for this position and the role an enterprise IT architect plays in assisting chief information officers (CIOs) and other decision makers in providing high-quality IT services. And get direction on how to get certified as an IT architect.

The role of the enterprise IT architect

There's a new kid on the block in information technology (IT) shops around the world. It's the IT architect -- the person who can transform business requirements into concrete IT realizations. With the rapid growth of emerging technologies and well-connected organizations relying on Web services and open standards to provide up-to-the-minute IT solutions for global business requirements, IT has had to respond with the creation of a single new position: the enterprise IT architect (EITA). After all, it isn't technology that solves business problems, it's human beings -- skilled people who understand the intricacies of a business issue as well as the complexity of potential information technologies that can be linked to resolve the problem.

The concept of an IT architecture or of the position of EITA isn't new. In fact, in every IT project, there should always be an architecture first and foremost. Compare it to building a house: If you don't have a plan to start with, the house will never get done. And if it does, the final product won't be anything like you imagined and probably won't be very functional. It's the same with IT projects. An IT project that doesn't start with a proper architecture is doomed to fail. Just like the house you want to build, an IT architecture helps you plan for system design, security, and protection -- helping you create a solid, stable construct that can weather the test of time.



Back to top


Map your vision to a design process

So, what does it take to be an EITA? First, it requires vision, or the ability to fully understand a business requirement, and then to match that vision to available tools and technologies to create a long-lasting solution. This skill is mostly evident in the enterprise IT architecture process, or the process of designing an enterprise solution to a specific business problem. It goes like this:

  1. Someone iterates a business requirement. (The requirement can be as complex as automating a supply chain among multiple vendors or creating an integrated workflow for automating the purchasing process.)
  2. This business requirement is handed off to the EITA. ("Do something with this, and do it yesterday" is the usual form the request takes. It is then up to the EITA to begin formulating a solution.)
  3. The EITA identifies the key stakeholders for this project. (This step requires a good understanding of the business itself.)
  4. The EITA must interview these key stakeholders to identify the components of the business process that can help solve the request. (This step includes not only the process that's required but also the players involved and their roles in the process.)
  5. The EITA finalizes the business process definition. (The stakeholders review it to ensure that everyone is on the same page.)
  6. When the business process is accepted, the EITA can create the initial budget for the project. (This budget will be refined as the solution is designed.)
  7. The EITA begins to look at potential solutions. (First, the EITA must review what is currently available in house. Ideally, the entire in-house IT architecture will be fully defined and will be readily available to the EITA.)
  8. Next, the EITA must determine whether the organization can support the solution implementation using existing capabilities or whether new capabilities are required.
  9. Identifying the required technologies lets the EITA refine the budget requirements.
  10. With refined budgets in hand, the EITA can provide the key stakeholders with a solution proposal. (This proposal is made in the form of a meeting in which the EITA provides documentation about the solution. The outcome of this meeting is a "go" or "no go" for the project.)

This process is illustrated in Figure 1. Although the EITA's job is far from done at this point, the elaboration of solutions of this type is one of the principal tasks an EITA handles.


Figure 1. The enterprise IT architecture process
Enterprise IT Architecture process


Back to top


It's lonely at the top

That's right. As an EITA, you'll often find yourself in a position where you're presenting a solution that no one is ready for. This is where the enterprise IT architecture process comes in handy. But, to be able to fulfill this process, you need specific skills -- the first of which, as mentioned earlier, is the ability to visualize business processes and potential IT solutions. In addition to this core skill, you need the following:

  • Change-management skills. The second most important skill is the ability to listen. EITAs must be good listeners, because no one likes change. Sometimes, this means that people aren't ready to accept the solutions you propose. So, take the time to listen to their needs -- both professional and personal -- and propose amendments to your solutions that take those needs into account.
  • Leadership. EITAs also need leadership skills, or the ability to provide direction during discussions and use solid interview skills to ask the right questions -- questions that immediately go to the heart of the matter, helping others visualize and understand the issue at hand.
  • Communication skills. Another important skill is the ability to communicate complex requirements in terms that every stakeholder can understand. The ability to "vulgarize" technological concepts in both oral and written communication can probably make or break any proposed solution. Often, this skill translates into the ability to illustrate key concepts and workflows in a clear manner.
  • Technological know-how. Of course, no other skill can supplement comprehensive technological expertise. Without this essential skill, no architect worthy of the name can even begin to propose any sort of solution. One of the best possible skill sets architects can have at this level is knowledge derived from having held many different positions within the IT organization. The best architects will have held operations, help desk support, systems administration, IT management, training, development, and other, similar positions within IT. This broad experience puts them in the unique position of having first-hand knowledge of the various IT roles, ensuring that the solutions they propose take every aspect of IT into consideration.
  • Extensive training. While formal training is not an absolute requirement for EITAs, it is important that candidates understand advanced architectural concepts, such as those proposed through official organizations such as the Information Technology Infrastructure Library (ITIL), architectural frameworks such as those proposed by Zachman and The Open Group Architecture Framework (TOGAF), and the standards outlined by the Institute of Electrical and Electronics Engineers (IEEE). Of course, technical training in various IT fields is also essential.
  • Organizational skills. Finally, EITAs need strong organizational skills to provide continued leadership as proposals unfurl into projects. The success of every IT project relies on a myriad of little details. Making sure that these details are taken care of during the execution of the project will make the difference between a successful undertaking and a total failure.

While this list of the skills an EITA requires isn't exhaustive, it does provide a good starting point for the evaluation of potential architect candidates.



Back to top


Do you have what it takes?

You're confident you've got what it takes when it comes to enterprise IT architecture. So prove it. The best way to do that is to go through an official IT architecture certification program. While several such programs are available, The Open Group IT Architect Certification Program stands out. This program provides two levels of certification: Certified IT Architect and Master Certified IT Architect. The first certification shows demonstrated architecture skills, but candidates still require some form of mentoring. The second certification demonstrates the skills to take on complete projects in a leadership role independent of others. The advantage of this program is that it's technology-agnostic and simply demonstrates that candidates have proven skills no matter which technology they choose to work with. Another interesting point of this program is that it can act as a source from which other organizations or professional societies can build their own certification programs. Finally, The Open Group provides a directory of Certified Architects, listing all who have passed the program and continue to maintain their certification level.



Back to top


Become the CIO's best friend

The EITA is extraordinarily gifted at solving IT puzzles. To do so, the EITA must have breadth of experience and excellent change-management and communication skills. This position is becoming increasingly important, especially with the overwhelming amount of work most top-level executives face in IT. When you propose and implement your first few IT solutions, you'll quickly discover that you've become the CIO's best friend. You'll see that CIOs are quite happy to rely on their EITA and soon hand off a considerable workload to this new role. In short, the EITA rapidly moves to become the CIO's right hand, helping him or her create solid, stable, and long-term IT solutions to the business requirements that come up every day.

Too many organizations flounder when it comes to having proper direction in IT. Having an EITA to rely on will help CIOs everywhere achieve their primary business goal: to give direction to their IT investments and keep budgets under control at all times. After all, IT is there to serve business, not the other way around.



Resources

Learn

Get products and technologies
  • IBM trial software: Build your next development project with IBM trial software, available for download directly from developerWorks.


Discuss


About the authors

Danielle Ruest

Danielle Ruest is a senior enterprise IT architect (EITA) focused on people and organizational issues for large IT projects. Danielle has been involved in the design and support of complex collaboration implementations, including deployment of technologies for e-mail, team sharing, and secure instant messaging. With her partner Nelson Ruest, she is the author of Preparing for .NET Enterprise Technologies, (Addison Wesley, 2001). and Windows Server 2003: Best Practices for Enterprise Deployments (McGraw-Hill Osborne, 2003) and participates in many webcasts and conferences. You can reach Danielle at architectures@reso-net.com


Nelson Ruest

Nelson Ruest is a senior enterprise IT architect (EITA) with more than 20 years of experience in migration planning and network, computer, server, and overall solution design (including MCSE, MCT, Microsoft MVP Windows Server). He has been a computer operator, a systems administrator, a trainer, a help desk operator, a support engineer, an IT manager, a project manager, and now, an IT architect. He was recently named a Microsoft Most Valuable Professional for the Windows Server product line. You can reach Nelson at architectures@reso-net.com.




Rate this page


Please take a moment to complete this form to help us better serve you.



 


 


Not
useful
Extremely
useful
 


Share this....

digg Digg this story del.icio.us del.icio.us Slashdot Slashdot it!



Back to top


Microsoft is a registered trademark of Microsoft Corp. Other company, product, or service names may be trademarks or service marks of others.