Pragmatic Enterprise Architecture sounds like a contradiction, right? We'll explain how an Enterprise Architect can contribute to innovation instead of focussing on control the IT assets.

1. Pragmatic Enterprise
Architecture
KdG
12 12 12
Erik Lenaerts
E2 Partners - Cronos

3. Enterprise Architecture
Minutes

4. The basics

5. An
Enterprise is an organization engaged in the trade of goods, services, or both to consumers.

6. Architecture
ISO/IEC/IEEE 42010 defines
requirements on the description of
system, software and enterprise
architectures. It aims to standardise
the practice of architecture description
by defining standard terms,
presenting a conceptual foundation
for expressing, communicating and
reviewing architectures and specifying
requirements that apply to
architecture descriptions, architecture
frameworks and architecture
description languages.

7. simple is
beautiful

9. CEO
Jeff Dunham
CFO
George Henry
CIO
Ted Cooper
VP Marketing & Sales
Karina Smets
Enterprise Architect
Steven Hills
IT Director
Kurt Cremers
IT Ops Director
Geert Bergs
VP HR
Stef Peeters

11. Why Enterprise Architecture?

12. Increasing complexity

13. Variation leads to complexity

15. Nha, that's not what I meant !

16. Yep, that's who I meant
C
?
C

17. Data quality?

18. Application Silo

19. If you don’t know where you are going, you'll end up somewhere else

20. Application Modernisation

21. Too many different...
Operating Systems
Database Management Systems
Server makes
Network components
Monitoring tools
Client computers
Anti Virus software
Firewall components
Development languages
...

22. The rise of the internet
•
•
•
•
Read Only
Focused on companies
Owning content
Directories - taxonomies
Web 1.0
•
•
•
•
Read Write
Focused on communities
Sharing content
Tagging - folksonomies
Web 2.0
•
•
•
•
Semantic web
Focused on individuals
Web of data
user engagement
Web 3.0

23. The Mobile World

24. What's your Architectural style?

26. Enterprise Architecture Approach

27. Where and when does an
Enterprise Architect contribute?

28. Gain traction and momentum

29. Progressive insights

30. Kaizen

31. Channel your energy

32. Work through the layers of complexity

33. Business drives IT

34. 1. Assess

35. Business
Data
Application
Technology

37. Interviews

38. Understand the business

39. Pain points
Needs

40. Determine impact - Finance, People, Process and
tools

41. Application Inventory

42. Application Inventory

43. User efficiency

44. Data models
Meta Data
models

45. Profiling

46. Technology Inventory

47. 2. Incept

48. Standardisation
html5, css3, xml, soap, rest, rdf, owl, saml, sql, http,...

49. Design & prototype

50. Get your troops involved

51. Build your vision

52. 3. Package

53. High end users
Expert users
Occasional user
Loyal followers

54. Scope your work
Remember to work in increments !

55. Work within business project borders.

56. Get improvements on the IT roadmap

57. Percent of time Google employees can spend
working on ideas and projects that interest them
20
%
Percent of Google's products that originated
from the innovation Time Off
50
%

58. 4. Sell

59. Features
Benefits

60. Align People

61. Prototype

62. Know your audience

63. Anticipate

67. Govern

68. Path of the Enterprise Architect

69. Skills of the Enterprise Architect

70. Treasure hunter

71. The generic specialist

72. Presentation skills

73. The diplomat

74. The salesman