The IT Architect Mantra

I came across this Software Architecture Mantra  from IASA

  • Systems that aren’t deployed don’t matter
  • Systems that don’t work don’t matter
  • Systems that don’t appease the users needs don’t matter
  • Systems that don’t perform don’t matter
  • Systems that aren’t health don’t matter
  • Systems that can’t be measured don’t matter
  • Systems that don’t add business value don’t matter

In my opinion it should be entitled The IT Architect Mantra.

Advertisements

Architect Agile Survival guide

  • Apply the ‘Prime the Pump’ principle

    In the prime the pump principle you look at the feature list of future iterations of an agile project. This looking ahead will help you plan for future architecture implications of the project. When the development team actually reaches one of the future iterations, you as the architect would have made your architecture decisions.

  • Just enough architecture

    As an architect you want to ensure that all architecture pieces are in place before handing it off to the developers; however in an agile project you usually do not have this luxury. The key is to develop an architecture that is enough to get the developers moving. You can take advantage of the iterative nature of agile by knowing you will review /update your initial architecture.

  • Wear multiple hats

    Don’t just be an architect on an agile project. Get your hands wet by writing some code, setting up infrastructure or even playing the role as P.M

IASA Associate courses

It was with great pleasure to learn that IASA will have online versions of its Associate Courses. I did the online version of IASA’s Core Architecture course and I was impressed by how the course was delivered.

There were a few hiccups: Internet availability issues and the switch to daylight savings times(there were students from all over the world and we had to ensure the switch to DST did not affect everyone). Despite the hiccups the course was well delivered and the presenter was knowledgeable about the subject.


Mirroring Cato and Socrates

 

 Oratory skills, as I have discovered, is one of the many skills required by a Systems Architect. In my quest to mirror Cato or Socrates, I was introduced to local Toastmasters Club.

Toastmasters gives one the opportunity to improve one’s public speaking skills. One of my favorite portions of my weekly Toastmasters meeting is what is called ‘Table topics”. In “Table Topics”, you are given the opportunity to practice your “off the cuff” speaking skills. This I have observed is an excellent skill for a Systems Architect.

 I am on a Communication Competency track in my local Toastmasters club. When I complete 10 speeches, I will receive my Communication Competency certificate. Ironically my second speech was about blogging.

 I am now trying to figure out my next speech. Maybe something technical- Cloud Computing, SOA, etc; however because of my fellow Toastmasters are from a diverse background, my next speech may have to be less technical.

 

The new architect

I recently moved from being a developer to the world of architecture. I have found a few websites that can help me as I make my architecture journey.