An Executive Summary
A step towards Improving business and return on investment for consultancies, Departments or team though TOGAF using the ADM, Enterprise Continuum, and Architecture Repository.
Why do I Care?
Often in everyday business we see unhappy clients due to missed commitment which does means that we may have to end up the business cycle with very low margins loosing client trust and annoying stakeholder’s.
Who are the stakeholders in my business?
2. People in sales
3. People in delivery.
What they all are Looking for with their specific viewpoints?
Return on Investment?
Is Investment only Money?
No !!! But money, skills, people and their time involved with steps of project execution are directly proportional to what the stakeholders get in return on their investment with their specific viewpoints?
Some invest money by hiring consultancies for business optimization and achieving their business goals. Few help them build their goals by investing time and experience to their business. Few invest in trainings learning and education to work for as consultant. But for all stakeholders it’s all that outcome matters in terms of time and money invested in the background and in different way’s.
We have allreday optimized ourselves what else?
How about trying a well-established enterprise architecture methodology to improve business process, technology and application stake and development life cycle helping us improve my return on Investment at our business unit level?
TOGAF set us guideline and process for enterprise architecture setup and improvement.
TOGAF defines "enterprise" as any collection of organizations that has a common set of goals. For example, an enterprise could be a government agency, a whole corporation, a division of a corporation, a single department, or a chain of geographically distant organizations linked together by common ownership.
The term "enterprise" in the context of "enterprise architecture" can be used to denote both an entire enterprise - encompassing all of its information and technology services, processes, and infrastructure - and a specific domain within the enterprise. In both cases, the architecture crosses multiple systems, and multiple functional groups within the enterprise.
Confusion often arises from the evolving nature of the term "enterprise". An extended enterprise nowadays frequently includes partners, suppliers, and customers. If the goal is to integrate an extended enterprise, then the enterprise comprises the partners, suppliers, and customers, as well as internal business units.
The business operating model concept is useful to determine the nature and scope of the enterprise architecture within an organization. Large corporations and government agencies may comprise multiple enterprises, and may develop and maintain a number of independent enterprise architectures to address each one. However, there is often much in common about the information systems in each enterprise, and there is usually great potential for gain in the use of a common architecture framework. For example, a common framework can provide a basis for the development of an Architecture Repository for the integration and re-use of models, designs, and baseline data.
Why do I need an enterprise architecture?
The purpose of enterprise architecture is to optimize across the enterprise the often fragmented legacy of processes (both manual and automated) into an integrated environment that is responsive to change and supportive of the delivery of the business strategy.
Today's CEOs know that the effective management and exploitation of information through IT is a key factor to business success, and an indispensable means to achieving competitive advantage. An enterprise architecture addresses this need, by providing a strategic context for the evolution of the IT system in response to the constantly changing needs of the business environment.
Furthermore, a good enterprise architecture enables you to achieve the right balance between IT efficiency and business innovation. It allows individual business units to innovate safely in their pursuit of competitive advantage. At the same time, it ensures the needs of the organization for an integrated IT strategy are met, permitting the closest possible synergy across the extended enterprise.
The advantages that result from a good enterprise architecture bring important business benefits, which are clearly visible in the net profit or loss of a company or organization:
v A more efficient business operation:
v Lower business operation costs
v More agile organization
v Business capabilities shared across the organization
v Lower change management costs
v More flexible workforce
v Improved business productivity
v A more efficient IT operation:
v Lower software development, support, and maintenance costs
v Increased portability of applications
v Improved interoperability and easier system and network management
v Improved ability to address critical enterprise-wide issues like security
v Easier upgrade and exchange of system components
v Better return on existing investment, reduced risk for future investment:
v Reduced complexity in the business and IT
v Maximum return on investment in existing business and IT infrastructure
v The flexibility to make, buy, or out-source business and IT solutions
v Reduced risk overall in new investments and their cost of ownership
v Faster, simpler, and cheaper procurement:
v Buying decisions are simpler, because the information governing procurement is readily available in a coherent plan
v The procurement process is faster - maximizing procurement speed and flexibility without sacrificing architectural coherence
v The ability to procure heterogeneous, multi-vendor open systems
v The ability to secure more economic capabilities
What specifically would prompt me to develop an enterprise architecture?
Typically, preparation for business transformation needs or for radical infrastructure changes initiates an enterprise architecture review or development. Often key people identify areas of change required in order for new business goals to be met. Such people are commonly referred to as the "stakeholders" in the change. The role of the architect is to address their concerns by:
Identifying and refining the requirements that the stakeholders have
Developing views of the architecture that show how the concerns and requirements are going to be addressed
Showing the trade-offs that are going to be made in reconciling the potentially conflicting concerns of different stakeholders
Without the enterprise architecture, it is highly unlikely that all the concerns and requirements will be considered and met.
What is an architecture framework?
An architecture framework is a foundational structure, or set of structures, which can be used for developing a broad range of different architectures. It should describe a method for designing a target state of the enterprise in terms of a set of building blocks, and for showing how the building blocks fit together. It should contain a set of tools and provide a common vocabulary. It should also include a list of recommended standards and compliant products that can be used to implement the building blocks.
Why do I need TOGAF as a framework for enterprise architecture?
TOGAF has been developed through the collaborative efforts of over 300 Architecture Forum member companies from some of the world's leading companies and organizations. Using TOGAF results in enterprise architecture that is consistent, reflects the needs of stakeholders, employs best practice, and gives due consideration both to current requirements and the perceived future needs of the business.
Developing and sustaining an enterprise architecture is a technically complex process which involves many stakeholders and decision processes in the organization. TOGAF plays an important role in standardizing and de-risks the architecture development process. TOGAF provides a best practice framework for adding value, and enables the organization to build workable and economic solutions which address their business issues and needs.
Who would benefit from using TOGAF?
Any organization undertaking, or planning to undertake, the development and implementation of an enterprise architecture for the support of business transformation will benefit from use of TOGAF.
Organizations seeking Boundaryless Information Flow can use TOGAF to define and implement the structures and processes to enable access to integrated information within and between enterprises.
Organizations that design and implement enterprise architectures using TOGAF are assured of a design and a procurement specification that can facilitate an open systems implementation, thus enabling the benefits of open systems with reduced risk.
Lots of Buzz Words, How Do we Start?
The first and foremost important thing is that we need someone who has gone through 1-2 successful cycle of such program.
He is outspoken as well as good listener and composer. He is able to understand multiple viewpoint and club them in to correct business lingo which is not just lingo but shows outcome and targeted results.
He is able to run improvement cycle by setting up enterprise continuum , running ADM cycles to improve processes at business technology and application layer.
structure all in to catalog of reusable tool sets in terms of process artefacts and reusable applications.
Set up Project, program application and technology portfolio management for the account.
He is able to initiate and complete setting up a 360 degree view of the organization goals and where we are heading so that all stake holders are aware of and find themselves involved to achieve the common goal rather than being dragged through hidden agendas.
What Is ADM?
The TOGAF ADM is the result of continuous contributions from a large number of architecture practitioners. It describes a method for developing and managing the lifecycle of an enterprise architecture, and forms the core of TOGAF. It integrates elements of TOGAF described in this document as well as other available architectural assets, to meet the business and IT needs of an Organization.
What is Enterprise continuum?
The Enterprise Continuum provides a framework and context to support the leverage of relevant architecture assets in executing the ADM. These assets may include architecture descriptions, models, and patterns taken from a variety of sources.
The practical implementation of the Enterprise Continuum will typically take the form of an Architecture Repository that includes reference architectures, models, and patterns that have been accepted for use within the enterprise, and actual architectural work done previously within the enterprise. The architect would seek to re-use as much as possible from the Architecture Repository that was relevant to the project at hand. (In addition to the collection of architecture source material, the repository would also contain architecture development work-in-progress.)
** Public available TOGAF specification