Link: http://weblog.tetradian.com/2011/08/30/how-not-to-define-bizarch/
Oh no, not again… Having all but crippled enterprise-architecture for the past decade with a muddled mess of myopia and misdefinitions, it seems Open Group are hell-bent on making the same kind of mess in business-architecture…
I need to be upfront about this: I don’t regard Open Group as ‘the bad guys’. Far from it: they’re an extremely important IT-standards body, and they do very important work indeed throughout the IT space. Yet it seems that whenever they touch anything that isn’t explicitly IT, they bring with them a perhaps-understandable yet entirely inappropriate IT-centric view of the world: and as a result, make a complete hash of it. Every darn time… And for the sake of all of us – including themselves – they really need to stop doing this…
On this occasion, it’s about business-architecture, specifically a transcript of Dana Gardner’s panel-session at the last Open Group conference, back in July: ‘PODCAST: Exploring business-IT alignment: A 20-year struggle culminating in the role and impact of Business Architecture‘. There’s a lot of good sense in there – no question about that – and for anyone involved in enterprise-architecture it’s definitely a ‘must-read’. Yet when I look at the sections that attempt to define business-architecture, and its relations to enterprise-architecture and IT-architectures, all I can do is weep:
[Dave van Gelder] Currently in the Business Architecture Working Group, we see business architecture as something that brings the balance between all the other architectures in the company — that’s IT architecture, financial architecture, money, people architecture, and a lot of other architectures. If business architecture is bringing the balance between the different aspects of a company, then business architecture is something that should be handled in the top of the organization, because balance should be created between all the different aspects in the organization.
(I was present at that start-up meeting Dave describes, by the way, at the Open Group conference in Lisbon back in 2006. A very good conversation then that unfortunately seems to have gone almost nowhere: the main point I remember was that I was perhaps the only person there who didn’t speak Dutch… 
)
Well, yes, that definition is fine, in its own way – except that that’s actually the linking role of enterprise-architecture. There’s no distinct ‘architecture of the business of the business’ here: in other words, no business-architecture. And it gets worse:
[Harry Hendrickx] When we look at the enterprise architect and the solution architect, the business architect focuses more on the complete implications of the strategy and technology trends on the operations, whereas the enterprise architect is more interested in the IT and the implications for the IT strategy and how IT should be deployed. The business architect is much more focused on the complete performance of the business operations.
In other words, despite Walter Stahlecker’s explanatory document for the Business Architecture Working Group back in 2008, and despite Len Fehskens’ excellent article on ‘Enterprise architecture’s quest for its identity‘ on the Open Group’s own weblog, the Open Group still fails to grasp the bald fact that enterprise-architecture is not an IT-role, and that the term ‘enterprise-architecture’ is not a synonym for ‘enterprise-scope IT-architecture’ – the latter being what is actually meant by ‘enterprise architect’ above.
As Len Fehskens makes clear in his article, enterprise-architecture is the architecture of the enterprise – and the enterprise (or extended-enterprise, if you prefer) extends not just beyond IT, but also a long way beyond the organisation itself. In enterprise-architecture, we develop an architecture for an organisation, but about the extended-enterprise or ‘ecosystem-with-purpose’ within which it operates. It’s also a much broader scope than the architecture of the ‘the business of the business’ – in other words, the domain-architecture that we would properly describe as ‘business-architecture’.
But what we have here is, unfortunately, yet another Open Group mess. Enterprise-architecture is sort-of defined as an IT role, tasked with bridging the gap between IT and ‘anything not-IT’. Business-architecture variously either takes on an organisation-centric variant of the real enterprise-architecture role (as in Dave van Gelder’s comment above), or a muddled mixture of ‘the architecture of everything not-IT’ (as in Harry Hendrickx’s comment) – the exact same IT-centric mistake as in Phase B of the TOGAF ADM. How this is supposed to help in bridging the infamous ‘business-IT divide’, when just about everything here will clearly increase it, I just do not know…
Perhaps the most worrying point, though, is this:
[Dana Gardner] Anyone else with some thoughts about how to make the certification and standardization of this stick? [Mieke Mahakena] What we’ve been doing in the Business Forum, after we decided that business architecture has its own reason for existence, we described the business architecture profession – what’s the scope and what should be the outcome of business architecture. Now, we’re working on the practice of business architecture by defining a framework, looking at methods, and defining approaches you can use to do business architecture.Parallel to that, if you know what the profession is and what the practice is, you’re able to create the business architecture certification, because those things help you define the required skills and experience a business architect needs. So, we are working on that in the Business Forum.
Why is this worrying? To see why, you need to click on the ‘Business Forum’ link. It takes you to a password-protected page – which, by examining the link, you’ll realise is only accessible to Open Group’s ‘Platinum’ members. The ‘big boys’: no mere mortals allowed here, thank you very much. Which should remind us, yet again, just how ‘open’ the Open Group actually isn’t: in fact, it operates a ‘pay for play’ membership, a straightforward hierarchy in which the only real rule is that the ‘big boys’ always win. So what we have in the Business Forum is a group of large IT-consultancies who’ve demonstrated over and over again that they have barely a freakin’ clue about anything beyond IT, supposedly defining the entirety of the business-architecture profession, discipline and certification, all of it behind closed doors, and with no input or review from anyone beyond IT. If you’re working in enterprise-architecture, and that fact doesn’t worry you, it should…
Again, some good ideas scattered throughout that transcript: but overall…? – well, perhaps the only word that could describe it is ‘yikes…’? Sorry, guys, but we definitely need to do better than this. Please?
Oh well.
