This slideshare will discuss a common implementation problem with TOGAF in the organization. Architecture and capability-based thinking takes the approach of understanding the characteristics of the problem and can be applied to IT, lines of business and throughout the organization. Feel free to follow me on Slideshare, LinkedIn or Twitter; I look forward to connecting.

1. Avoid a Common TOGAF® Implementation
Pitfall
TOGAF® is a registered trademarks of The Open Group in the United States and
other countries. All other trademarks are the property of their respective owners.
http://tamimrahman.com
Slide 1

2. TOGAF® is a Specification for Architecture
It describes considerations for
creating architecture in an
organization, it does not
provide explicit instruction on
how to do architecture
Example: A driver’s handbook
will describe the rules of the
road but it will not instruct
you on how to drive
TOGAF® identifies what needs to be thought of when
understanding the outcome sought; it does not prescribe.
http://tamimrahman.com
Slide 2

3. Process Flow vs. Work Flow
The ADM is a process flow; it
describes the steps followed in
developing architecture:
The scope of the Enterprise and
architecture, the problem to solve
and expected outcome, obstacles to
overcome throughout the
architecture domains, considerations
for solution selection and supported
transition plan, solution
implementation and change
management
http://tamimrahman.com
Slide 3

4. But… there are key questions that need to
be answered before applying the ADM:
What disciplines
need to be involved?
Who will be consuming the architecture?
http://tamimrahman.com
Slide 4

5. “What level of detail is required?”
This question is often the most difficult for architects to answer. The
answer depends on the stakeholders that are consuming the
architecture and the architect’s understanding of the decision that they
are making.
Architecture is the understanding of the obstacles that need to be
overcome to achieve a desired result. It provides a criteria to assess
possible solution options and is therefore critical to the decision maker.
Avoid having the decision maker select a solution option, understand
the outcome they want and describe what performance will enable this
outcome; this is the capability concept. This will allow you to focus on
the obstacles that need to be resolved and your sponsor to elaborate on
the outcome they want to achieve.
http://tamimrahman.com
Slide 5

6. The Capability Concept and Lifecycle
Unites People, Process and Technology to realize an outcome.
Capabilities have a lifecycle and require:
• Different levels of detail and abstraction with their own: governance,
obstacles, expertise and competencies
http://tamimrahman.com
Slide 6

7. Architecture is Performed at Each Phase
Line of Business Management:
-Leverage organizational strengths
What needs to change?
Physical
Architecture
Logical
Architecture
Conceptual
Architecture
Contextual
Architecture
Senior
Management:
-organization
identity &
industry
position
Why change?
Business Transformation Professions:
-Implement the change in the organization
How will change be performed?
Operations:
-Exploit and
leverage the
change
With what tools
are we realizing
value?
The ADM is used to create architecture throughout each phase.
http://tamimrahman.com
Slide 7

8. TOGAF® Supports the Capability Concept
Strategic
Intent
http://tamimrahman.com
People
Process
Technology
We use TOGAF® to
leverage the
organization’s
business capabilities
to achieve the
business vision (i.e.
outcome); we need
to better understand
capabilities
Slide 8

9. Next Steps…
Learn more about Capability-Based Thinking:
• Free Download: Business Transformation Made Straight-Forward
Contact me for more information:
Twitter: tamim_rahman
LinkedIn: ca.linkedin.com/in/tamimrahman/
Website: http://tamimrahman.com
http://tamimrahman.com
Slide 9