Does Agile Enterprise Architecture = Agile + Enterprise Architecture?

Download Does Agile Enterprise Architecture = Agile + Enterprise Architecture?

Post on 04-Jul-2015




4 download

Embed Size (px)


Does Agile EA Equal Agile Plus EA? Confusion over the word agile is actually one of the challenges with Enterprise Architecture (EA) today. So, what does "agile" -- or in some quarters, "Agile" -- mean today, and how do we apply Agile to architecture? Most people use the phrase "Agile Architecture" to refer to software architecture appropriate for Agile software development projects -- not EA at all. Nevertheless, there is a growing Agile EA movement that extends the core principles of the Agile manifesto to EA more broadly. This approach deemphasizes the role of frameworks and other artifacts, and instead treats the enterprise as a complex adaptive system. Agile EA thus leverages complex systems theory, including the role of emergent properties, to rethink how organizations innovate and otherwise deal with change within the context of market and regulatory constraints. Attendees of this session will: * Gain clear differentiators between Agile software architecture and Agile EA * Understand the role of complex systems theory to the practice of Agile EA * Learn how Bloomberg Agile Architecture(tm) can support organizations' agility requirements in the future


  • 1. Copyright 2014, Intellyx, LLC1Does Agile EA =Agile + EA?Jason

2. About Jason Bloomberg President of Intellyx Advise companies on their digitaltransformation initiatives & help vendorscommunicate their agility stories Write for Forbes, Wired, &DevX on Digital Transformation Buy my latest book,The Agile ArchitectureRevolutionCopyright 2 2014, Intellyx, LLC 3. The Agile ManifestoManifesto for Agile Software DevelopmentWe are uncovering better ways of developingsoftware by doing it and helping others do it.Through this work we have come to value: Individuals and interactions over processesand tools Working software over comprehensivedocumentation Customer collaboration over contractnegotiation Responding to change over following a planThat is, while there is value in the items onthe right, we value the items on the left more.Copyright 3 2014, Intellyx, LLCSource: 4. Context: SoftwareDevelopment Focus on small teamsthat crank out code Iterative, self-organizing,collaborative Focus on creatingworking softwareWell-run Agile development meansproducing a lot of good softwarequicklyCopyright 4 2014, Intellyx, LLCPhoto Credit: Phil Whitehouse 5. What about Architectureon Agile Projects? We dont need no stinkinarchitecture! Architecture lumped in withdocumentation (less is more) Architects slow downdevelopers Architects produce artifactsthat arent Agile Lead to extra workCopyright 5 2014, Intellyx, LLCPhoto Credit: Yortw belief that Agile andArchitecture dont mix 6. But we Do NeedArchitecture! Software architecture Appropriatemodularization ofcode Selection ofappropriatecomponents & libraries Integration strategy Systems architecture Scalability of distributed application Cloud deployment issues Availability, caching, etc.Copyright 6 2014, Intellyx, LLC 7. Create Minimum ViableArchitecture All documentation,artifacts, diagrams,etc. are means to anend Dont architect morethan thestakeholders want Problems: Shortsighted Leads to legacyissues Limits agilityCopyright 7 2014, Intellyx, LLCPhoto Credit: Camera Eye Photography 8. Defer Commitment onDesign Decisions Traditional architecturecompleted beforedevelopment On Agile projects,tentative architecturegood enough Commit to designdecisions in appropriateiteration/sprintCopyright 8 2014, Intellyx, LLCPhoto Credit: Wade Rockett 9. The Overbuilding Paradox How do stakeholders knowwhat flexibility they willrequire? How generalized shouldcode be? When to build capabilitiesvs. when to buildaffordances?Copyright 9 2014, Intellyx, LLCPhoto Credit: Ishikawa Ken 10. Capabilities vs.Affordances Capability Ability to perform orachieve certainoutcomes throughfeatures or functions Apps have capabilities Affordance A property of an object which allows an individualto perform an action Tools have affordances Depends upon how user wants to use toolCopyright 10 2014, Intellyx, LLCPhoto Credit: EraPhernalia Vintage 11. Why Agile SoftwareArchitecture isnt Agile Agile movement focuses on working software Focus on getting the software to meet itsrequirements Get all roadblocks out of the way Agile-built software is coded to be fit for purposeCopyright 11 2014, Intellyx, LLCPhoto Credit: B4bees 12. Instant Legacy Difficult to upgrade Systems areinflexible Impossible toreplace Difficult tocustomize Challenge tointegrate Expensive over timeCopyright 12 2014, Intellyx, LLCPhoto Credit: LHOON 13. The Goal of AgileSoftware Requirement to build software that responds tochanging requirements Inherent flexibility vs. rapid development &deploymentCopyright 13 2014, Intellyx, LLCPhoto Credit: Robert Couse-Baker 14. Scaling Agile for theEnterprise EnterpriseArchitecture context Organization,process, technology,and information Legacy context Existing applications,middleware, systems of record Business focused, iterative, get stuffto work, iconoclasticCopyright 14 2014, Intellyx, LLCPhoto Credit: Boston Public Library 15. Different Meanings ofAgile Agile-with-a-capital-A Software development thatfollows the Agile Manifesto General meaning of agile Business agility as propertyof an organizationCopyright 15 2014, Intellyx, LLCPhoto Credit: Earl McGehee 16. Business Agility Responsiveness Tactical value Resilience Risk mitigation Innovativeness Strategic valueCopyright 16 2014, Intellyx, LLCPhoto Credit: Masonite Burn to respond to change in thebusiness environment and leveragechange for competitive advantage 17. Responsiveness The ability to respondquickly and efficiently to(potentially) positive changein the business environment Changing customer demand Changing marketplaceenvironment Changing supply chainfactors Tactical driverCopyright 17 2014, Intellyx, LLCPhoto Credit: Good Eye Might 18. Resilience The ability to respondquickly and efficiently tonegative change in thebusiness environment Managing risk Bouncing back fromadverse events Disaster recovery Security breach response Regulatory changeresponse Tactical driverCopyright 18 2014, Intellyx, LLCPhoto Credit: Joe 19. Innovativeness The ability to introduce change into the businessenvironment in order to achieve a strategicadvantage New products or services Expand market share Enter new marketsCopyright 19 2014, Intellyx, LLCPhoto Credit: Kay Kim 20. Wheres Our BusinessAgility? Organizations must be responsive, resilient, andinnovative Business agility is a property of the enterprise People and technology can be flexible as well,but we must architect our organizations to beagileCopyright 20 2014, Intellyx, LLCPhoto Credit: Stuart Berwick 21. Introducing ComplexAdaptive Systems Systems of systemsthat exhibit emergentproperties Properties of systemas a whole Component systemscan be human,technology, etc. Self-organizingCopyright 21 2014, Intellyx, LLCPhoto Credit: DirectDish 22. Enterprise as ComplexAdaptive System Business agility isproperty of organizationas a whole, hence anemergent propertyof the organization Enterprise is system ofsystems that exhibitsemergent properties System of people andtechnologyCopyright 22 2014, Intellyx, LLCPhoto Credit: agu2000_de 23. Engineering a ComplexSystem Architecture focuses on the overalldesign of a system How all components of the systemmust work together to achievebusiness goals Engineering focuses on the best wayto build and run a system Lifecycle best practices (qualityassurance, deployment, updates, etc.) Compliance with architectureAgile principle: respond to change overfollowing a planCopyright 23 2014, Intellyx, LLCPhoto Credit: Brent 2.0 24. At the Heart of AgileArchitecture Think of the enterprise as a system of systems Component systems are people and technologysystems We must architect the organization so entireenterprise exhibits businessagility We can only engineerbusiness agility via itscomponent systems Change is constant & howchanges to componentsystems affect the enterprise is unpredictableCopyright 24 2014, Intellyx, LLCPhoto Credit: nickodoherty 25. Complex vs. TraditionalSystems Avoid emergent properties in traditional systems Traditional system: given requirements, build torequirements Complex system: establish initial conditions andrules for behavior ofcomponent systems,and emergence takescare of itself Feedback loops arecommonCopyright 25 2014, Intellyx, LLCPhoto Credit: Franco Folini 26. The Secret to Emergence Rules that affect behavior ofcomponent systems can bevery simple Emergent behaviors oftenunpredictable Try something, see whathappens, repeat Feedback loops & iterativeapproachesCopyright 26 2014, Intellyx, LLCPhoto Credit: Juan Leis Agile to You? 27. Attractors for ComplexSystems Stable Emergent behaviors die out ornever occur Not applicable to enterprise Cyclical System bounces between two ormore well-defined states Also not applicable Chaotic Unpredictable, few discernable patterns Normal state for enterprise Agile Exhibiting desired emergent behaviorsCopyright 27 2014, Intellyx, LLCPhoto Credit: Anders Sandberg 28. Architecting ComplexSystems Coherence of system If emerging behavior strays from desired outcome,have pre-established means for bringingorganization back in line Feedback loops Gather & analyze data on emergent behavior tocorrelate with initial constraints and determinenext course of action Mimics natural selection Favor desired behavior and discourage undesirablebehavior, and system will adapt to changedenvironmentCopyright 28 2014, Intellyx, LLC 29. Agility vs. Flexibility Flexibility is the ability of acomponent system to deal withchange within a specified set ofparameters People can be flexible vs. rigid intheir decision making Software can be flexible if it isconfigurable to behave differentlygiven different requirementsCopyright 29 2014, Intellyx, LLCPhoto Credit: Joe Goldberg 30. Does Flexibility Lead toAgility? If your people and yoursoftware are flexible, doesthat make your organizationagile? Necessary, perhaps, butdefinitely not sufficient Being able to changeinflexible software quicklydoesnt necessary make itflexibleCopyright 30 2014, Intellyx, LLCPhoto Credit: A. Drauglis 31. Architecting Enterprise asComplex System Architect people as well as technology Very different sets of activities Emergent behaviors oftenunpredictable Continual adjustment necessary Automation critical for ensuring agility Small changes to component systembehavior may lead to significantemergent behaviors Butterfly effectToo slow and youre not agile!Copyright 31 2014, Intellyx, LLCPhoto Credit: Diganta Talukdar 32. Architecting People? Governance: creating, communicating, andenforcing policies Apply to both human & technology behavior Policy-related processes Automated & lightweight Focus on important policies Security Regulatory compliance Software interface standardsNot a traditional approach to governance!Copyright 32 2014, Intellyx, LLCPhoto Credit: Dave Catchpole 33. Governance as AgilityEnabler Simple rules & policies lead tocomplex emergent behavior Which ones lead to agility? Levels of governance Low-level rules & policies Departmental Organizational Governance has negative connotation Reputation for limiting productivity Governance, Risk, & Compliance tools integrated intraditional mannerCopyright 33 2014, Intellyx, LLCPhoto Credit: Mike Lewinski 34. Bimodal IT: The WrongWay Digital Team Self-organizing Fast-moving May followAgile at leastin spirit Littlegovernance Traditional IT Hierarchical Slow-moving Waterfall-centric Formal,bureaucraticgovernanceCopyright 34 2014, Intellyx, LLCPhoto Credit: Keith Williamson Shadow IT is Result 35. Rethinking Bimodal IT Business-driven transformation of traditional IT Iterative Opportunistic legacy modernization Cross-cutting reorganization to DevOps culture Increased collaboration with digital teams Move towardcontinuousdevelopment &integrationCopyright 35 2014, Intellyx, LLCPhoto Credit: Andrew Magill automation of governance 36. Shifting Role ofGovernance Old Way Paperwork-heavy Morale-killing policies & procedures Bureaucratic & slow Scar tissue that impedesinnovation New Way Highly automated Focus on edge cases wheregovernance is essential Depends on dynamic constraint satisfactionCopyright 36 2014, Intellyx, LLCPhoto Credit: Pascal 37. Governance & Agility? Do we get business agility? Agility doesnt mean chaos If everybody in anorganization did whateverthey wanted to without anyrules or policies Rules & policiesinconsistentlycommunicated or applied Secret to business agility is to empower peopleto innovate within constraints of organizationalpolicyCopyright 37 2014, Intellyx, LLCPhoto Credit: Pascal 38. Introducing BloombergAgile Architecture Bloomberg AgileArchitecture reinventsEnterprise Architecture(EA) to drive businessagility across theorganization New architecture paradigm EA technique focused onarchitecting agilityCopyright 38 2014, Intellyx, LLC 39. Extending the AgileManifesto Individuals and interactions overprocesses and tools As a system of people & technology,the enterprise is more about people Working software over comprehensivedocumentation Technology must actually work toenable agility Customer collaboration over contractnegotiation Slice across the silos Responding to change over following aplan Architect for changeCopyright 39 2014, Intellyx, LLCPhoto Credit: Mary Margret 40. Bloomberg Agile ArchitectureMind MapCopyright 40 2014, Intellyx, LLC 41. Goal of Agile Architecture BAA is a technology-driventechnique Specific approaches forleveraging moderntechnologies like CloudComputing & Big Data Analyticsto achieve business agilitygoals of the organization Goal of architecture Connect the dots between theenterprise agility drivers &necessary technology changesto achieve goals of businessCopyright 41 2014, Intellyx, LLCPhoto Credit: Whitney Waller 42. Agile EA & ArchitectureFrameworks Architecture frameworks (TOGAF, Zachman,DoDAF, etc.) do not adequately address bu...


View more >