Albus Consulting Limited | Agile Architecture
post-template-default,single,single-post,postid-50881,single-format-standard,qode-core-1.0.3,ajax_fade,page_not_loaded,,brick-ver-1.4, vertical_menu_with_scroll,smooth_scroll,wpb-js-composer js-comp-ver-4.5.3,vc_responsive

Agile Architecture

Everything has to be agile nowadays.  This includes things strategy through to infrastructure.  Even your Enterprise Architecture.  It’s a bitter pill to swallow for environments that have worked so hard to normalise things, only to now to be called out for having become structured. The opposite it seems of agile.


For years many of us have struggled to describe our environments, and our data, in an effort to gain some level of control that also helps to mitigate risk and allows our beloved ITIL processes to function properly.  This has resulted in hundreds or thousands of pages of documentation.  Great effort went into establishing this wealth of information about how our environments were configured, built, installed, patched, maintained.


And a document is only so good as long as it is updated with the latest information.  Hence, Change Management.  The Architecture Review Board (ARB) and the Change Advisory Board (CAB) has for years been the very thing we would use to meet out order and has for just as long been the measure by which our maturity as IT organisations has been measured.


What further has not helped any ideas around agility has been the general adverse attitude by auditors to the risks associated with not having properly running ARBs and CABs.  And so we have lived and died by our adherence to this array of measures and attitudes that in the end made us slow, unresponsive, risk adverse and very non-agile.  Solid but stolid.


Now however the game has changed.  Excitement is in the air!  Business is at last starting to be more IT aware!  But does it mean that they have the same passion for the risk adverse environment we have created?  Does it mean they now suddenly appreciate our ARBs and CABs?  Sadly not.


See the sea change lies in the fact that, very much like photography, IT has transitioned from the sphere of the arcane dark magicks of yesterday to the commonplace commodity of current culture.  In the past photographers were purloining precious pearls of captured life from closed crimson closets and the art was acquired by the avid.  Now its point ‘n shoot.


So IT has been demystified.  And its practitioners are daily being stripped of their star speckled satins.  In ripping the curtains right back the consumers are finding less risk than they had expected.  And they are finding the value that convenience offers.  To be fair to the artisans, IT has really not been this safe until recently.


In response we have to rapidly adapt and show some value.


Hence agile.  Hence aiming at the very core of things by adopting an agile architecture.  But how?


We do this by polishing up one of our dearly held principles, and lifting it to prominence.  The principle in question is keeping things ‘loosely coupled’.  Every solution has to meet is requirement, that is a given.  But the now also holds the ability for most solutions to be less dependent on its environment.  And it is this very dependence on the environment that has spawned the ARBs and CABs.  By the measure you remove the dependence, you remove the requirement for ARBs and CABs.


So this means quite a lot of things for your IT environment.  Give us a call to explore this.

No Comments

Post a Comment