Implement successful and cost-effective enterprise architecture projects. This book provides a new approach to developing enterprise architecture based on the idea of emergent behaviors—where instead of micromanaging system implementation, the enterprise architecture effort establishes clear goals and leaves the details to the implementation teams. System development efforts are measured based on their contribution to achieving business goals instead of implementing specific (possibly outdated) requirements. Most enterprise architecture initiatives employ one of the existing system architecture frameworks such as Zachman or The Open Group Architecture Framework, but these are not well-suited for enterprise architecture in a modern, agile organization. The new approach presented in this book is based on the author’s experience with large enterprise architecture efforts. The approach leverages research into complex adaptive systems and emergent behaviors, where a few simple rules result in complex and efficient enterprise behaviors. Simplifying the task of establishing and maintaining the enterprise architecture cuts the costs of building and maintaining the architecture and frees up those resources for more productive pursuits. System implementers are given the freedom to rapidly adapt to changing user needs without the blessing of the enterprise modeling priesthood, and the architecture is transformed from a static pile of obscure models and documents into an operational framework that can be actively used to manage an enterprise’s resources to better achieve business goals. The enterprise architect is free to stop focusing on building and maintaining models and start focusing on achieving business goals. What You’ll Learn Refocus enterprise architecture on business needs by eliminating most of the enterprise-level models Delegate tasks to the development teams who do system implementation Document business goals, establish strategies for achieving those goals, and measure progress toward those goals Measure the results and gauge whether the enterprise architecture is achieving its goals Utilize appropriate modeling techniques that can be effectively used in an enterprise architecture Who This Book Is For Architecture practitioners and architecture managers: Practitioners are experienced architects who have used existing frameworks such as Zachman, and have experience with formal architecture modeling and/or model-based system engineering; managers are responsible for managing an enterprise architecture project and either have experience with enterprise architecture projects that were ineffective or are looking for a different approach that will be more cost-effective and allow for more organizational agility. Government program managers looking for a different approach to make enterprise architecture more relevant and easier to implement will also find this book of value.

As the digital economy changes the rules of the game for enterprises, the role of software and IT architects is also transforming. Rather than focus on technical decisions alone, architects and senior technologists need to combine organizational and technical knowledge to effect change in their company’s structure and processes. To accomplish that, they need to connect the IT engine room to the penthouse, where the business strategy is defined. In this guide, author Gregor Hohpe shares real-world advice and hard-learned lessons from actual IT transformations. His anecdotes help architects, senior developers, and other IT professionals prepare for a more complex but rewarding role in the enterprise. This book is ideal for: Software architects and senior developers looking to shape the company’s technology direction or assist in an organizational transformation Enterprise architects and senior technologists searching for practical advice on how to navigate technical and organizational topics CTOs and senior technical architects who are devising an IT strategy that impacts the way the organization works IT managers who want to learn what’s worked and what hasn’t in large-scale transformation

Enterprise Architecture is the discipline of managing the complexities of the Business-IT landscape. It has been around since the 1980's, when for the first time computers were connected in networks, and the already serious (and unsolved) problem of the complexity of computer programs for relatively simple business needs turned into the huge problem of large networks of them in complex business landscapes. In spite of many 'best practices' and 'frameworks' that have been introduced, Enterprise Architecture is not a great success. After thirty years, we still have the same problems. Chaos is still everywhere. Projects still fail far too often. In this book, (hidden) assumptions behind the existing approaches to enterprise architecture are challenged, and a more realistic perspective that helps us battle the complexities and unpredictabilities of today's Business-IT landscapes is described. Practical suggestions about enterprise architecture governance and products, based on real-world experience with the described approach, complete the book. From general management to IT professionals, everyone who is confronted with the problem of managing Business-IT landscapes can profit from the insights this book offers. No specialist prior knowledge is required. Gerben Wierda is author of Mastering ArchiMate, and was, amongst other things, Lead Architect of the Judiciary in The Netherlands, Lead Architect of APG Asset Management, and is now Team Coordinator Architecture & Design at APG. He holds an M.Sc in Physics from the University of Groningen and an MBA from RSM Erasmus, Rotterdam.

Dismantle the overwhelming complexity in your IT projects with strategies and real-world examples from a leading expert on enterprise architecture. This guide describes best practices for creating an efficient IT organization that consistently delivers on time, on budget, and in line with business needs. IT systems have become too complex—and too expensive. Complexity can create delays, cost overruns, and outcomes that do not meet business requirements. The resulting losses can impact your entire company. This guide demonstrates that, contrary to popular belief, complex problems demand simple solutions. The author believes that 50 percent of the complexity of a typical IT project can and should be eliminated—and he shows you how to do it. You’ll learn a model for understanding complexity, the three tenets of complexity control, and how to apply specific techniques such as checking architectures for validity. Find out how the author’s methodology could have saved a real-world IT project that went off track, and ways to implement his solutions in a variety of situations.

"Reaching the Pinnacle: A Methodology of Business Understanding, Technology Planning, and Change (Implementing and Managing Enterprise Architecture)" by Samuel B. Holcman explains the detailed process of building an enterprise architecture. Samuel B. Holcman brings his strategic business plans to business and technology professionals with "Reaching the Pinnacle: A Methodology of Business Understanding, Technology Planning, and Change (Implementing and Managing Enterprise Architecture)." In order to bring a method to the madness that can often be today's business structure, Holcman uses "Reaching the Pinnacle" to introduce the process of building an enterprise architecture. Holcman uses his 40 years of experience as a leading trainer and consultant in enterprise architecture in writing "Reaching the Pinnacle." He explains enterprise architecture as the rethinking of how business planning and information technology work together in order to achieve strategic goals. "Reaching the Pinnacle" explains how an organization and its important departments can achieve their goals through a series of project initiatives. Holcman offers a simple, easy-to-understand way to implement an enterprise architecture project into one's organization. "While the approach is not quick - it may take up to a few years to transform an organization - my methodology provides an effective means for moving the organization from its as-is state to its desired state in an iterative manner," says Holcman. Holcman's methods and approach have been used by numerous Fortune 500 companies and have led him to be the top consultant on the topic. He believes the 'for practitioners, by practitioners' approach of "Reaching the Pinnacle" will make the book a crucial resource among business and technology personnel everywhere. "Reaching the Pinnacle: A Methodology of Business Understanding, Technology Planning, and Change (Implementing and Managing Enterprise Architecture)" is available for sale online at Amazon.com, directly from the author at www.PinnacleBusGrp.com, and other channels. REVIEW COPIES AND INTERVIEWS AVAILABLE

Organizations today exist in an environment of unprecedented change. They do so against a backdrop of a global, competitive marketplace, the fast-paced enablement of technology, amplified regulation and accelerating organizational complexity. Many organizations are addressing change in a sub-optimal way and they are operating without a clear view of where their operational risks lie. It is these dynamics that are leading organizations to recognise and embrace Business Architecture. Despite this environment, Business Architecture can be a difficult ’sell’ - it is often perceived to be abstract and lacking in tangible delivery. To succeed, Business Architecture must be pragmatic and, to be sustainable, it must focus on achieving long-term value and, at the same time, recognise the shorter-term tactical needs of the organisation. With these challenges in mind, this book provides a practical guide on how to employ Business Architecture and how to build a balanced proposition that delivers value to a broad range of stakeholders. As the book states, Business Architecture should not be practised in isolation, nor should it be thought of as a one-off process; it needs to be woven into the fabric of the organization. And so the authors illustrate the opportunities for weaving the Business Architecture Practice into this fabric through the various stakeholders and life cycles that exist, both formally and informally, within an organization. Whilst recognizing best practice, this book explores a new, inspirational level of Business Architecture whilst acknowledging that the best way to realize the vision is one step at a time.

This book is positioned as a rst in a series of books on enterprise architecture needed for a Master of Enterprise Architecture program, and is targeted both at university students and practitioners with a drive to increase their understanding of these elds. As an introductory book, this book aims to explore the concept of enterprise architecture. At rst glance, writing such an introductory book might seem as a straight forward task of setting up a structure and lling in “the blanks. ” However, writing this book turned out to be a pleasant journey of discovery. Based on our past experiences, each of us had a clear understanding of enterprise architecture, based on several years of experience and insight in the eld. However, when we started writing this book, and each of us exposed our individual understandings, it became apparent that our understanding of the eld differed in several ways. This prompted several discussions leading to an abundance of new insights. Without exception, thesediscussionstookplaceina pleasantandopenatmosphere,fueledbyourshared driveforunderstandingandincreasedinsight. Wearenowevenmoreconvincedthan before, that the eld enterprise architecture is a true multi-disciplinary profession. In the resulting book, we would like to share our insights, while also hoping to continue our discussions, now also involving you as a reader. We also realise that the journey is still far from complete. While this introductory book provides an overview of the eld of enterprise architecture from the perspective of our insights, many aspects need further re nement.

Organizational complexity is an unavoidable aspect of all businesses, even larger ones, which can hinder their ability to react to sudden or disruptive change. However, with the implementation of enterprise architecture (EA), businesses are able to provide their leaders with the resources needed to address any arising challenges. A Systemic Perspective to Managing Complexity with Enterprise Architecture highlights the current advances in utilizing enterprise architecture for managing organizational complexity. By demonstrating the value and usefulness of EA, this book serves as a reference for business leaders, managers, engineers, enterprise architects, and many others interested in new research and approaches to business complexity.

Dismantle overwhelming IT complexity with a practical methodology and real-world solutions. Dismantle the overwhelming complexity in your IT projects with strategies and real-world examples from a leading expert on enterprise architecture. This guide describes best practices for creating an efficient IT organization that consistently delivers on time, on budget, and in line with business needs. IT systems have become too complex and too expensive. Complexity can create delays, cost overruns, and outcomes that do not meet business requirements. The resulting losses can impact your entire company. This guide demonstrates that, contrary to popular belief, complex problems demand simple solutions. The author believes that 50 percent of the complexity of a typical IT project can and should be eliminated and he shows you how to do it. You ll learn a model for understanding complexity, the three tenets of complexity control, and how to apply specific techniques such as checking architectures for validity. Find out how the author s methodology could have saved a real-world IT project that went off track, and ways to implement his solutions in a variety of situations.

Based on an extensive study of the actual industry best practices, this book provides a systematic conceptual description of an EA practice and offers practically actionable answers to the key questions related to enterprise architecture.