Oct 042009
 

I added Roger Sessions, CTO of ObjectWatch to my blogroll today. I have been following Roger on Twitter @RSessions particularly his posts and discussions on IT Complexity and how it relates to IT project failures.  On Thursday, Oct 8th Roger and I shared a conference call and agreed to investigate opportunities to collaborate on IT complexity based on Roger’s work on Simple Iterative Partitions.

I will be speaking with our staff and our IT faculty to see how we might be able to integrate lessons on complexity into courses and programs at BCIT.

Thanks for the insights Roger and I hope to contribute to the discussion. Keep it up!

Jul 142009
 

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!

Foster adaptation: leaders must develop ‘next practices’ while excelling at today’s best practices.” In 2005, we established the Strategic Practices groupin our IT Services department. This group role is responsible for the development, maturation and integration of a broad set of IT disciplines and methodologies across all areas of IT Services. These disciplines are intended to raise the level of rigor and reliability of all of our technical implementations while ensuring that IT investments are aligned with institutional strategy. The Strategic Practices group includes practices like enterprise architecture, business analysis, project management, business continuity, IT security, risk management and performance management. Think of these as our ‘next practices’.  At the same time, we adopted the IT Infrastructure Library (ITIL) framework for standardizing, managing and measuring our core service delivery. So far we have implemented the Service Desk function, Incident Management, Change Management, Problem Management, Asset Management and are building out Configuration, Capacity and Availability Management processes. These are today’s best practices.

May 162008
 

Over time, technology provides more and more functions and hopefully value to your enterprise. The challenge is how to manage the complexity that comes with technology. I started my IT career as an IBM 360 mainframe computer operator managing VM/CMS and DOS/VSE CICS systems. IT architectures were relatively simple. One large computer, a few large boxes for hard disk drives, several tape drives and an a large line printer. For the most part, our clients interacted with printouts and some lucky ones got access to 3270 green screen terminals.

Think about today … while our technology provides a very functionally rich environment for delivering value to our organizations, the technological complexity has gone through the roof.

Delivering our ERP in 1992 took one IBM RS/6000 RISC box with Oracle 6 RDBMS and Oracle forms installed on all client PCs. Now we need a P Series Server running AIX (Unix) for the Oracle database, VMWare Servers running SUSE (Linux) for the Oracle Application Server(s), Load Balancers, DNS servers, DHCP Servers, Novell network servers and various workstations (PCs running Windows XP and IE 6 or 7 with client side Java)!!!

So how do we as Enterprise Architects manage complexity? We created an Application Portfolio with attributes about the components that the applicaiton requires like:

  • identity store
  • web enabled
  • database server o/s
  • application server o/s
  • web server o/s
  • web server
  • database
  • application development environment
  • etc ..

We have over 200 applications with at least 7 distinct solution delivery platforms:

  • Oracle – J2EE
  • LAMP
  • Microsoft – .Net
  • Lotus Domino
  • Sun
  • Apple
  • Novell

Now we are working on the second year of our Technology Plan (rolling 3 year window). As part of this we will be looking to favour “depth in our technology choices over breadth”. We will focus on Oracle, LAMP and Microsoft. Investing in these solution platforms will allow us to focus our people on a managed set of technologies and be able to more rapidly respond to our clients needs.

Anyone else thinking “Deep instead of Wide”??

Switch to our mobile site