Overview

For those of you who are impatient, here are the principles:

Don t confuse this work with any of the excellent books on enterprise architecture. Enterprise architecture is used to describe how businesses are structured, the processes they perform, the data they produce and consume, and their supporting technical systems. IT is first and foremost a business area, and as such, can also be the subject of an enterprise architecture analysis the purpose of this book. This book is an application of enterprise architecture principles (process, data, and systems analysis) upon the domain of large-scale enterprise IT itself.

Therefore, the first principle is build an architecture. Understand your IT processes, functions, data, and enabling systems an architecture effort no different from any other line of business.

Identify and integrate across your functional silos. View your IT organization as a single value chain producing operational services, from initial business contact through requirements, development, release, operations, maintenance, and retirement.

Establish your key IT performance metrics and apply standard business intelligence best practices to gain cross-functional visibility while clarifying and managing your data quality and lineage.

Formalize the things you manage: processes, services, applications, projects, technical platforms, and their dependencies and road maps. Integrate enterprise architecture with portfolio and configuration management to support this.

Analyze your internal IT data for redundancies, and establish defined systems of record. Collect the majority of IT operational data and information as part of core value chain activities, not in one-off point initiatives especially dependencies, the most expensive and...