Scribd
Upload
13 views

10-steps-for-preparing-a-togaf-project

The document outlines 10 essential steps for preparing a successful Enterprise Architecture (EA) project using the TOGAF ADM framework. Key steps include understanding the organization, clarifying principles, aligning governance, formalizing the EA function, customizing TOGAF to fit specific needs, and establishing a central architecture repository. Following these steps can help ensure that EA projects meet their goals and deliver value.

Uploaded by

nishant.kulshrestha
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
13 views

10-steps-for-preparing-a-togaf-project

The document outlines 10 essential steps for preparing a successful Enterprise Architecture (EA) project using the TOGAF ADM framework. Key steps include understanding the organization, clarifying principles, aligning governance, formalizing the EA function, customizing TOGAF to fit specific needs, and establishing a central architecture repository. Following these steps can help ensure that EA projects meet their goals and deliver value.

Uploaded by

nishant.kulshrestha
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

10 STEPS

For Preparing A TOGAF Project

Many Enterprise Architecture (EA) projects fail to meet their


goals. Following these 10 steps will help to deliver a successful EA
project using the TOGAF ADM
1.
Understand
2.
Identify
EA practitioners need to know
how and why an organization Knowing the business itself

operates, in order to be able to is not enough, however.


explain how architecture work Architects also need to identify
will benefit them. Knowing how the driving factors behind
a firm operates is a standard the industry and sector of the
responsibility for architects, firm, as no business exists in

3. 4.
but too many forget why, i.e., a vacuum. These factors must
to increase value, reduce costs, be reflected in the design of
manage risk, etc. the architecture.

Clarify
Architects might understand
Principles
the business and its
Architecture principles need
surroundings, but does the
to be based on business
business understand them?
principles. Often, EA can end
EA practitioners need to know
up disconnected from the
what their expectations are.
business, meaning principles
TOGAF projects will involve a
need to be agreed and defined
variety of stakeholders across
before projects are initiated.
the organization, and failing to
account for this can derail work.
5.
Governance
6.
Frameworks
Business principles are not Capability Maturity Models

the only area that EA needs to should be utilized to

conform with; the governance determine organizational

framework of the firm must readiness and identify

also align with EA governance. the key characteristics

A lack of alignment can to measure. TOGAF 9.2

undermine the credibility and possesses predefined maturity

7.
consistency of EA deliverables. assessments such as CMMi

8.
that are well suited to this.

Maturity
Formalize
Sustainable architecture needs a
formalized EA function. Formalize Sustainable architecture needs a

HR to assist with succession formalized EA function. Formalize

planning, skills development, HR to assist with succession

resource allocation, and planning, skills development,

performance management, resource allocation, and

ensuring that the resources of the performance management,

EA function reflect the complexity ensuring that the resources of the

of the organization. EA function reflect the complexity


of the organization.
9.
Customize
TOGAF 9.2 is an evolving framework
that has been designed to work across
a huge variety of sectors. As such, each
individual EA should customize their
TOGAF implementation to suit their
unique needs. This needs to be backed
up with documentation, to ensure
smooth progress if the team or purpose
changes.

Repository

10.
A powerful central architecture
repository is essential for maintaining
a sustainable EA practice. Fortunately,
this is easily accomplished with an EA
tool like iServer365, which has been built
around its central repository.
© Copyright 2020 Orbus Software. All rights reserved.

No part of this publication may be reproduced, resold, stored in a retrieval system, or distributed in any form or by any
means, electronic, mechanical, photocopying, recording, or otherwise, without the prior permission of the copyright owner.

Such requests for permission or any other comments relating to the material contained in this document may be submitted
to: [email protected]

Orbus Software
Floor 4, 60 Buckingham Palace Road, SW1W 0RR
+44 (0) 20 3824 2907
[email protected]
www.orbussoftware.com

You might also like