Enterprise Architecture in Higher Education

On August 11th, Gartner announced a “new approach for enterprise architecture” that they labelled “Emergent Architecture”.  I got a chance to read some responses from Todd Biske, Mike Rollings, and Dion Hinchcliffe.  Thanks for the great insights and commentary.

In the press release, Bruce Robertson, Gartner Research VP states the two characteristics of “Emergent EA”:

1. “Architect the lines, not the boxes – which means managing the connections between the different parts of the business rather than the actual parts of the business themselves.”
2. “It models all relationships as interactions via some set of interfaces, which can be informal and manual”

On characteristic 1. is if you only look at the connections between parts of the business, how can you look for opportunities to reduce complexity, increase efficiency and implement reusability? I believe enterprise architecture is about the whole organization and its environment, not just pieces of it. As an example, our EA practice encompasses IT Service Management (ITIL), Business Analysis (BA) and Program Management (PMO).

On characteristic 2. , again all this says to me is to take a “user experience” approach to describing the architecture. This is nothing new as far as I can tell … perhaps I am missing something?  Read more...

Andy Blumenthal wrote a great post “Adaptive Leaders Rule the Day“. In his post, Andy reviewed a Harvard Business Review July 2009 article “Leadership in a (Permanent) Crisis” and commented on the article’s insights on adaptive leadership.

I really liked Andy’s quote “Leaders need a proverbial “toolkit” of successful behaviors to succeed and even more so be able to adapt and create innovative new tools to meet new unchartered situations.”

Andy listed some of the successful behaviours in the “toolkit”.  I recommend you read the full article to get all of Andy’s insights. 

Here is the list of successful behaviours:

• “Foster adaptation”
• Stabilize, then solve
• Experiment
• “Embrace disequilibrium”
• Make people safe to question
• Leverage diversity

Taking a similar approach to my previous post on Generative EA Principles, I will explore and share how Andy’s list of behaviours fit with our EA practice (and maybe yours).  We have a long way to go to fully leverage the successful behaviours but having some clear names for what we have accomplished helps.  Thanks Andy!  Read more...

Tomorrow, I will be asking my peers in the Internet2 ITANA – IT Architects in Academia to do a peer review of a Technology Lifecycle taxonomy that we use at BCIT. As we developed our Enterprise Architecture, we needed a way to communicate not only the lifecycle of initiatives and technology but also their viability.

Here is what we use:

Here are the definitions that we use:

Watching:
- includes initiatives and technologies that are being watched for maturity in industry

Researching:
- includes initiatives and technologies that are currently under consideration, investigation or evaluation for future implementation

Investing:
- includes initiatives and technologies that are the target of resources including financial investments and/or investments in human resources

Sustaining:
- includes initiatives and technologies that deliver services identified in the Core Services Catalogue or in Service Level Agreements

Containing:
- includes initiatives that have been completed and technologies that are in the process of being phased out

End of Life:
- includes initiatives and technologies that are being retired from service

While this is a life cycle, it is not mandatory that an initiative of technology follows through every step.  Read more...