The document discusses the challenges posed by organizational silos and the limitations of cloud computing in achieving business agility. It emphasizes the need for an agile architecture that transcends traditional methods and integrates various organizational elements to enable responsiveness and innovation. The author, Jason Bloomberg, advocates a new approach to enterprise architecture focused on architecting agility to address these issues.

1. Copyright © 2014, Intellyx, LLC
1
Breaking Down
Enterprise Silos
in the Cloud
Jason Bloomberg
President
jason@intellyx.com
@theebizwizard

2. About Jason Bloomberg
• President of Intellyx, Global Advisory Firm focused
on Architecting Agility
– Formerly with ZapThink 2001 - 2013
• Global thought leader in the areas of Agile
Architecture, Cloud Computing, EA, & SOA
• Created the Licensed ZapThink
Architect (LZA) SOA course &
associated credential
• Run the Bloomberg Agile Architecture
Certification Course around the world
• Buy my newest book,
The Agile Architecture Revolution
• Include @theebizwizard in tweets
Copyright © 2014, Intellyx, LLC2

3. Problems of
Organizational Silos
• Every line of business,
department, functional area
has its own requirements, its
own way of doing things
• Must invest in specialized
components for narrow
purposes
• IT must integrate everything,
increasing cost, complexity, &
brittleness
Copyright © 2014, Intellyx, LLC3
PhotoCredit:DocSearls,https://www.flickr.com/photos/docsearls/5500118475/sizes/o/

4. Silos on Top of Silos
• Organizational silos
– Lines of business,
departments,
geographic locations,
etc.
• Application silos
– COTS apps / bespoke
apps for different
departments
• Infrastructure silos
– Varied data centers &
rooms, heterogeneous
platforms, & Cloud!
Copyright © 2014, Intellyx, LLC4
PhotoCredit:CalDellingerhttps://www.flickr.com/photos/cstreetus/3381285199/sizes/o/

5. It’s Time to Take Down
the Silos!
PhotoCredit:SavannahRiverSite,http://www.flickr.com/photos/51009184@N06/
Copyright © 2014, Intellyx, LLC5

6. Cloud is No Panacea
• Move to the Cloud! Save money!
• But…problems with technical silos persist:
– Apps that aren’t architected for Cloud
– Static interfaces
– Legacy technology
– Inconsistent policies,
rules, & processes
– Crusty old middleware
that predates Cloud
– Diverse versions of
truth
– Semantic interoperability
issues
Copyright © 2014, Intellyx, LLC6
PhotoCredit:PhilipLearahttps://www.flickr.com/photos/philleara/7046670573/sizes/l

7. The Cloud Agility
Challenge
• Application silos in the
Cloud are still silos
• “Cloud” more than IaaS
+ PaaS + SaaS
– Extend to mobile,
Internet of Things, etc.
• Enterprise context
– Dealing with legacy
– Hybrid scenarios
– Complex governance &
compliance challenges
Copyright © 2014, Intellyx, LLC7
PhotoCredit:MarioGiambattistahttps://www.flickr.com/photos/mariogiambattista/3857244187/sizes/l

8. Business Agility
• Responsiveness
– Tactical value
• Resilience
– Risk mitigation
• Innovativeness
– Strategic value
Copyright © 2014, Intellyx, LLC8
PhotoCredit:MasoniteBurnhttps://www.flickr.com/photos/masonite-burn/6273626739/sizes/l
Ability to respond to change in the
business environment and leverage
change for competitive advantage
Ability to respond to change in the
business environment and leverage
change for competitive advantage

9. Enterprise as Complex
Adaptive System
• Business agility is
property of organization
as a whole, hence an
emergent property
of the organization
• Enterprise is system of
systems that exhibits
emergent properties
• System of people and
technology
– Traffic jams
– The wave
Copyright © 2014, Intellyx, LLC9
PhotoCredit:agu2000_dehttps://www.flickr.com/photos/38123550@N00/166930597/sizes/o/

10. The Secret to Emergence
• Rules that affect behavior of
component systems can be
very simple
• Emergent behaviors often
unpredictable
• Try something, see what
happens, repeat
• Feedback loops & iterative
approaches
Copyright © 2014, Intellyx, LLC10
PhotoCredit:JuanLeishttps://www.flickr.com/photos/kaibara/4632384645/sizes/l
Sound Agile to You?Sound Agile to You?

11. Governance as Agility
Enabler
• Simple rules & policies lead to
complex emergent behavior
– Which ones lead to agility?
• Agility vs. Chaos
• Levels of governance
– Low-level rules & policies
– Departmental
– Organizational
• Governance has negative connotation
– Reputation for limiting productivity
– Governance, Risk, & Compliance tools integrated in
traditional manner
Copyright © 2014, Intellyx, LLC11
PhotoCredit:MikeLewinskihttps://www.flickr.com/photos/ikewinski/9430887561/sizes/l

12. Limitations to Business
Agility
• IT as the “bad guy”
• EA buried in the IT
department
• Ivory tower architecture
• Silo mentality
– Not invented here
– Can’t wait for IT
– BYOD to BYO-everything
• No Agile Architecture
Copyright © 2014, Intellyx, LLC12
PhotoCredit:HarrisWalkerhttps://www.flickr.com/photos/harriswalkerphotography/3340161598/sizes/l

13. What is Bloomberg Agile
Architecture?
• Bloomberg Agile Architecture
reinvents Enterprise Architecture
(EA) to drive business agility across
the organization
• NOT: software architecture compatible
with Agile development methodologies
– Won’t support the organization’s agility
requirements
• New architecture paradigm
• Style of EA focused on architecting agility
Copyright © 2014, Intellyx, LLC13

14. Bloomberg Agile Architecture
Mind Map
Copyright © 2014, Intellyx, LLC14

15. Cross-Cutting
Architecture
• Organization,
process,
applications, data,
infrastructure
• Role for Enterprise
Architecture
• Wakeup call for EAs
& their
organizations
• Essential for
addressing silos
Copyright © 2014, Intellyx, LLC15
PhotoCredit:penguincakeshttps://www.flickr.com/photos/penguincakes/2831662803/sizes/l

16. Extending the Agile
Manifesto
• Individuals and interactions over
processes and tools
– As a system of people & technology,
the enterprise is more about people
• Working software over comprehensive
documentation
– Technology must actually work to
enable agility
• Customer collaboration over contract
negotiation
– Slice across the silos
• Responding to change over following a
plan
– Architect for change
Copyright © 2014, Intellyx, LLC16
PhotoCredit:MaryMargrethttps://www.flickr.com/photos/double-m2/4384578534/sizes/l

17. The Transformative Role
of Automation
• Cloud automates
operational environment
• DevOps as automation-
driven organizational
change
• Big Data automation
• SOA Governance
automation
Copyright © 2014, Intellyx, LLC17
PhotoCredit:wiredforlegohttps://www.flickr.com/photos/wiredforsound23/6813264988/sizes/l
DevOps as Model for
Cross-Cutting Architecture
DevOps as Model for
Cross-Cutting Architecture

18. From DevOps to “BizOps”
• Before: dev chucking code to test, then over wall
to ops
• Now: continuous test, continuous deployment
• In progress: responsiveness to continuous
requirements change & variation
Copyright © 2014, Intellyx, LLC18
PhotoCredit:fdecomitehttps://www.flickr.com/photos/fdecomite/12598505695/sizes/l

19. Avoiding the Overbuilding
Problem
• The challenge of minimum viable design
• Code to metadata to unified system abstraction
• If you have an overbuilding problem, you’re
doing Agile Architecture wrong!
Copyright © 2014, Intellyx, LLC19
PhotoCredit:dalvejahhttps://www.flickr.com/photos/dalvenjah/33560737/sizes/l

20. What are You Writing?
• Code?
– Least flexible, most susceptible
to overbuilding, reuse always a challenge
• Metadata via declarative programming?
– Abstracts code, but leads to complexity shell game
• Abstract models?
– Essential for
implementable
Agile Architecture,
but vendors
largely fall short
Copyright © 2014, Intellyx, LLC20
PhotoCredit:daviddhttps://www.flickr.com/photos/puuikibeach/6989179273/sizes/l

21. Assembling the Pieces of
Agile Architecture
• Architecting for change
requires working at higher
levels of abstraction
• Abstract models resolvable
to capabilities at run time
– Dynamic coupling
– Dynamic schemas
– Extreme late binding
Copyright © 2014, Intellyx, LLC21
Architect for ChangeArchitect for Change
PhotoCredit:PaulioG4eordiohttps://www.flickr.com/photos/pauliogeordio/2308703486/sizes/l

22. Dynamic Coupling
• Tight coupling
– Must code all nodes at
once
• Loose coupling
– Interfaces abstract
underlying code
• Dynamic coupling
– Interfaces resolved at run
time
Copyright © 2014, Intellyx, LLC22
PhotoCredit:GordonRobertsonhttps://www.flickr.com/photos/gordon_robertson/5507645738/sizes/l

23. Dynamic Schemas
• Rigid data schemas
– Entity-Relational
Model, XML Schemas
• Schemaless data
– Problem of implied
schemas
• Dynamic schemas
– Metadata modeled at
design time, resolved
at run time
Copyright © 2014, Intellyx, LLC23
PhotoCredit:JuhanSoninhttps://www.flickr.com/photos/juhansonin/2317185234/sizes/l

24. Extreme Late Binding
• Early binding
– Traditional integration
• Late binding
– Web Service discovery
– Content-based routing on
ESBs
– DNS resolution for RESTful
endpoints
• Extreme late binding
– Fully dynamic discovery
– Resolve URIs & metadata
references in real time
Copyright © 2014, Intellyx, LLC24
PhotoCredit:RalphRepohttps://www.flickr.com/photos/ralphrepo_photolog/4079285574/sizes/l

25. Dynamic Constraint
Satisfaction
• Governance as layers of policies & rules
• Need to calculate effective policy
• Cross-process, cross-organization, in & out of Cloud
• In real time
Copyright © 2014, Intellyx, LLC25
Process “A” Team “C”Division “B”
Cross-Process
Governance

26. No Excuses!
• Business Agility
platforms are now
available
• Business wants agility
• IT can provide agility
• Architects should know
how to architect agility
– Take my class!
Copyright © 2014, Intellyx, LLC26
PhotoCredit:JosephBremsonhttps://www.flickr.com/photos/excitingsounds/9908052865/sizes/l

27. Jason Bloomberg
President, Intellyx
jason@intellyx.com
@theebizwizard
Thank You!