Shahid Shah is an expert in enterprise architecture, business architecture, and information security with over 20 years of experience. The document discusses common pitfalls that prevent enterprise architecture efforts from achieving business agility. It provides tips for measuring business agility and ensuring architecture products are useful to end users. The key takeaway is that enterprise architecture succeeds when it is pragmatic, fit for its purpose, and useful in enabling rapid and adaptable decision making.
Strategies for Landing an Oracle DBA Job as a Fresher
Enterprise Architecture and Agility
1. Chasing business agility using
Enterprise Architecture (EA)
Common EA pitfalls
By Shahid N. Shah, CEO
2. NETSPECTIVE
Who is Shahid?
• 20+ years of business/enterprise architecture, design,
software engineering, and information assurance
(security) in embedded, desktop, and enterprise
environments such as
– FISMA-regulated government systems
– FDA-regulated medical devices and systems
– HIPAA-regulated health IT systems
• Have held positions at CTO, Chief Architect, or
Enterprise Architect in a variety of regulated
environments
www.netspective.com
2
3. NETSPECTIVE
What’s this talk about?
Background
•
•
What it means to chase business
agility
What happens when we business
owners don’t get agility from their
Enterprise Architecture (EA) and
business architecture (BA) efforts
www.netspective.com
Key takeaways
•
•
There aren’t perfect scripts to follow
for BA/EA success but there are
numerous mistakes to avoid
Which BA/EA key practices lead to
the most success
3
4. It’s hard to create BA and EA
that end-users actually find
useful in their pursuit of solving
real-world business problems.
www.netspective.com
4
5. NETSPECTIVE
How do you know if your business is agile?
Agility is hard to define but it’s easy to see when it’s missing
Speed of response
to new customer
needs
Mapping of
strategic initiatives
to customer needs
vs. enterprise needs
www.netspective.com
Permission-oriented
culture
Value generation
efficiency for
enterprise initiatives
Coupling vs.
Teaming between
enterprise
components
Number of Shadow
IT systems
Business-use EA
artifacts vs. tech use
artifacts
Compliance-focus
vs. customer focus
5
6. NETSPECTIVE
What can you measure?
If you can’t measure it and can’t document it, does it exist?
Customer acquisition,
engagement, or
retention focused
metrics
Product roadmap
focused metrics
Process efficiency
metrics
www.netspective.com
Top line revenue
metrics
Logistics and product
delivery metrics
Margin metrics
(bottom line)
Technical and IT
metrics (apps,
sunsets, TCO)
6
7. NETSPECTIVE
Focus on the real customer
Inside-out focus
IT
Personnel
Unsophisticated and
less agile focus
www.netspective.com
Outside-in focus
Corporate
Users
Partners
Corporate
Customers
Sophisticated and
more agile focus
7
8. Your EA and BA is successful when
its activities are pragmatic, fit for
purpose, and useful.
You’ve failed if you haven’t created a framework
for rapid and adaptable decision making.
www.netspective.com
8