On extending TOGAF's business-architecture to a whole-of-enterprise scope (presentation at Biner/OpenGroup EA conference, Stockholm, December 2010)

1. Unpacking Business Architecture Tom Graves , Tetradian Consulting TOGAF Stockholm, November 2010 info@tetradian.com / www.tetradian.com 3 Dec 2010 (c) Tom Graves / Tetradian 2010

2. Business architecture and the enterprise or, What to do when the enterprise impacts on the business

5. Let’s just step back a bit... ...think about this in strict architectural terms

7. Use the TOGAF maturity-model 3 Dec 2010 (c) Tom Graves / Tetradian 2010

8. TOGAF scope in maturity-model 3 Dec 2010 (c) Tom Graves / Tetradian 2010 TOGAF 8.1 TOGAF 9 (...everything else is just ‘detail stuff’) Main emphasis of TOGAF, for IT-architecture only ‘ Big-picture’ strategy Pain-points + wicked-problems But business most wants us to work on these...

18. So where does TOGAF fit into this? ...or, how would we use TOGAF for this type of architecture?

19. We need a more balanced view... 3 Dec 2010 (c) Tom Graves / Tetradian 2010 “ everywhere and nowhere is ‘the centre’ of the enterprise-architecture”

20. ...current TOGAF is too parochial? 3 Dec 2010 (c) Tom Graves / Tetradian 2010 “ IT-infrastructure is the centre of the enterprise-architecture” (but there’s a whole world out there beyond IT...)

24. Step 1: Context and patterns ...or, rethinking the real pattern behind TOGAF Phases B, C and D

27. Scope of enterprise-architecture (complete EA includes many other intersecting ‘architectures’ – security, process, brand, organisation etc)

28. Step 2: Layering and cycles ...or, where Zachman really works with TOGAF

30. Layers of abstraction (row-0 = ‘always’; rows 1-5 = far-future to near-future; row-6 = past)

31. Cycles of structural dependency (adapted from classic Group Dynamics project-lifecycle and VPEC-T framework)

32. Strategy, tactics, operations (overall cycle and relationships need to be in balance)

33. The ‘quick-money’ failure-cycle (this was a key source of problems for the bank – too short-term focus, with the classic “last year +10%” used as a substitute for strategy)

34. Step 3: Consistency for models ...or, service-oriented architecture for the whole enterprise