I was impressed with Cathay Pacific Airways have created a set of metrics for measuring Enterprise Debt and was struck by the fact they’d omitted the word ‘technical’ from the description. I think the debt metaphor is very powerful for explaining why businesses should pay attention to architecture but I do feel we should not only consider the technical debt, we should also understand the ‘debt’ created by ill-considered processes and hard-to-grasp strategies (all part of EA IMO). Some questions I’m pondering:
What would a 360 degree set of metrics for Enterprise Debt look like? Would VPEC-T analysis help? How can we create a board level visualisation of ED and make a a key tool for a ‘Managing Complexity’ agenda and guide decision-making when designing business change? All thoughts for my long flight home at the end of the week. Here’s a link to a piece from my friend Charles Edwards on Enterprise Technical Debt that added to my thoughts: http://www.agileea.com/portal/index.php?option=com_content&view=article&id=110:what-is-enterprise-technical-debt&catid=51:enterprise-architecture-&Itemid=54 Nigel Green5Di Ltd.
Mobile: +44 (0)7818 53 22 43
Web: www.5dinnovation.com
Sent from my iPad
