www.outsystems.com© OutSystems – all rights reservedThe changing role of theEnterprise ArchitectNuno BaptistaExpert Servic...
www.outsystems.com© OutSystems – all rights reservedGet to know itEA translates business vision andstrategy into effective...
www.outsystems.com© OutSystems – all rights reservedGet to know itWhat is changing?• Strategic thinker• Business Oriented•...
www.outsystems.com© OutSystems – all rights reservedNew challenges of EA rolePromote IT-Business alignment#1Accelerate inn...
www.outsystems.com© OutSystems – all rights reserved• Understand your business• Prioritize your application portfolio#1 Pr...
www.outsystems.com© OutSystems – all rights reservedSupport the enterprise strategyManage a prioritized application portfo...
www.outsystems.com© OutSystems – all rights reserved• Adopt Pace Layered model– Flexible governance models– Try and Fail f...
www.outsystems.com© OutSystems – all rights reserved#2 – Adopt Pace Layered model
www.outsystems.com© OutSystems – all rights reserved#2 – Try and Fail fast
www.outsystems.com© OutSystems – all rights reserved#2 – Try and Fail fastBuilt a prototype• Innovative idea• Delivery Eff...
www.outsystems.com© OutSystems – all rights reserved#2 – Try and Fail fastChallengeWhat is your innovative idea thatwill c...
www.outsystems.com© OutSystems – all rights reserved• Avoid becoming legacy– Design for Change#3 Maximizeinvestment return...
www.outsystems.com© OutSystems – all rights reserved• Measure cost of maintenance• Build vs buy approach• Build with a tec...
www.outsystems.com© OutSystems – all rights reserved#3 - Design for Change
www.outsystems.com© OutSystems – all rights reserved• Built in Non-Functional Requirements (NFRs)• Deliver fast• Change fa...
www.outsystems.com© OutSystems – all rights reserved• Migrate DBMS from SQLServer 2005 to Oracle 11g.• Migrate OutSystems ...
www.outsystems.com© OutSystems – all rights reservedPerformantScalableDocumented AuditableMaintainable#4 – Built in NFRsPo...
www.outsystems.com© OutSystems – all rights reserved#4 – Deliver fast, change fasterDevelopmentModel driven developmentred...
www.outsystems.com© OutSystems – all rights reservedNew challenges of EA rolePromote IT-Business alignmentUnderstand your ...
www.outsystems.com© OutSystems – all rights reserved
www.outsystems.com© OutSystems – all rights reservedThank you!Nuno BaptistaExpert Services Managernuno.baptista@outsystems...
Upcoming SlideShare
Loading in...5
×

The Changing Role of The Enterprise Architect

806

Published on

An exploration of new challenges faced by enterprise architects, including: promoting business alliance, innovation, and budgeting

Published in: Business, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
806
On Slideshare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
33
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • DefinitionEnterprise architecture is an ongoing business function that helps an 'enterprise' figure out how to execute best the strategies that drive its development.
  • Technology is used pervasively to enable, automate, streamline, and transform business processes of every description. At its very best, enterprise architecture articulates the full range of possibilities for a business, even describing how to go about getting there.The most common misconception? … that it’s a function of IT?
  • Enterprise Architects are theonesresponsible to define theroadmapof IT to achievethestrategyTalkaboutthe EA pitfallsGlorified developerExceptions are the ruleNo budget for changeLate governanceNo business engagement
  • Promote IT-Business alignmentSupport business innovation Maximize technology investment returnsConstantly reduce costs
  • EAs are not just Technology delivers, they are the enablers of business strategy developmentSo, is fundamental to understand what are the business rules.Internally, EAs must have a clear vision about business values, priorities, targets and achievements.
  • EA must talk to all related parts (CEO, IT, Biz)
  • meetings are going to become less like office space and more like star wars.
  • Explain place layerThere is a mismatch of technologicalapplication cycles and business cycles due, for instance, to intensive competition.Applications change at different paces to support the business.Different models of governance and SDLCs are required at each layer to balance risk and rate of change.Using the same governance models to every applications using a single layer prevents innovation in IT. EAs must be the owners of this new governance models that are adapted to the business needs.Eas must understand and adapt the application portfolio to the new governance models to drive the innovation inside the organization.Relaxed or restricted policies regarding documentation, performance, integration, testing, development best practices must be adapted to each layers.Applications move down from outer layers as they become more business critical and stable.
  • Explain what is the greenway application.BiZideia – All those rich guys waiting for a 30 min line to pass the security checkpoint… maybe they are willing to pay not to wait?Keep in mind that even the non successful projects are also less expensive.This application already pass from the innovation to differentiation layer during his growth.Imagine a 3 months project that didn’t fit the business process or had a technology handicap?This idea came from am EA!
  • Explain what is the greenway application.BiZideia – All those rich guys waiting for a 30 min line to pass the security checkpoint… maybe they are willing to pay not to wait?Keep in mind that even the non successful projects are also less expensive.This application already pass from the innovation to differentiation layer during his growth.Imagine a 3 months project that didn’t fit the business process or had a technology handicap?This idea came from am EA!
  • Start smallAlign with a business needManagement sponsorship for business processes changesFast quick fixes, to get the business trustMeasure the benefitRequest for feedbackEvaluate user adoption
  • Siebel system will be all refactored and upgraded to a new version (1,5 year project). But why, it does not respond to the business needs.Creating another legacy. They fail to understand why they have legacy systems in the first place, and just rush into creating another one. They don't understand the requirement for on-going change, nor does the business encourage them to think about it. This could be due to: a lack of process - i.e. they don't understand how to facilitate change at each stage of the life-cycle; or, stakeholders unwillingness or inability to express requirements for change.It’s must easier to sell a revolutionary idea than a evolutionary ideaOnce you have a framework to help you: - measure cost of maintenance - continuously decrease cost of change - create a differentiating layer of applications, that can easily become mission critical - create an innovation layer of applications, that allows the business to experiment with low cost and under control - understand what and when to discontinue, and doing it aggressivelyGet packages for the commodity, discontinue old stuffDon’t over customize commodity systems
  • Not cleanly separating the legacy from the new solution. A proper service architecture is not developed that is truly independent of the legacy systems, and so the new solution remains tightly coupled to the legacy. Not designing for change.It isn't just a matter of creating a more agile implementation built with finer-grained components and servicesNot cleanly separating the legacy from the new solution. The two become entwined storing up an even bigger legacy problem for the future. For example, a proper service architecture is not developed that is truly independent of the legacy systems, and so the new solution remains tightly coupled to the legacy. Even though they may use loosely coupled technology such as web services, their content and behavior is just a direct reflection of the legacy system.Not designing for change. Agility isn't just a process - as in agile development - agility is also an analysis and design requirement. Ensuring a new solution is better able to respond to change than the legacy systems it is replacing requires appropriate techniques throughout the life cycle. It isn't just a matter of creating a more agile implementation built with finer-grained components and services, but also understanding the business's requirements for agility and identifying those components and services in a way that aligns with that. Conversely, you don't need to over-compensate and waste time providing too much agility where it is not needed - although, that is always going to be difficult to predict...
  • Built in NFR removes a tremendous work of the EAs freeing him to focus on the strategy and business values.Regarding Reducing Costs, OutSystems Platform is the best companion of an EA.Broadly, functional requirements define what a system is supposed to do whereas non-functional requirements define how a system is supposed to be. Some examples are: Usable, Reliable, Portable, Available, Auditable, Documented, etc.To deliver a complete solution including the NFRs, an EA must know that the NFRs are part of the Architecture Best Practices of the project and the team effort is far from neglected.
  • I would like to share with you a project we did in an insurance company.In a process of standardization technology, meaning reducing costs, the customer decided to migrate his database management system from SQLServer to Oracle. The challenge was simple.What is the value for the business? None! Just risk Let’s see how we can do it without spending to much money.Don’t spend money just to keep your systems running.EA,pleasetrythisatyourhome!
  • Started by analyzing the solution documentation and change some SQL statements, followed by a data migration and solution deployment.The upgrade was done successfully, still performance issues were raise and tackled without writing a single line of code.Like this customer EA can benefit from the non functional requirements compliance that the most demanding companies have.EAs can be more focus in strategic goals rather than in the KTLO dilema.We did it in 2 platforms with 24h and 1h of downtime.This process took 20 days of total effort.
  • 1- The Agile Platform allows you to develop at a different level of abstraction than writing code C# or java. You have to deal with an order-of-magnitude less complexity than when you build an application in native languages. Integrations are also very simple - not only to deliver, but to manage over the life of the application. 2- OutSystems Platform have built-in dependency analysis which allows you to understand the impact of anything you do, not just on one application, but across your application portfolio built with the Agile Platform. Second, every change will always have all the non-functional requirements delivered so you never have to spend time and money worrying about things like security, scalability, maintainability, documentation, performance, auditing, all that stuff. It's built-in every time.  3 - From an operational perspective, the Agile Platform fully automates the deployment process. Because it is highly automated you never run the risk of putting something in production that doesn't work. Every application has built-in performance monitoring, logging and full auditing making trouble shooting and performance management easy. You don't code for this, you get it out of the box with every application you deliver. When you build applications with the Agile Platform, they're all delivered very quickly and they're change-ready from day one.
  • The Changing Role of The Enterprise Architect

    1. 1. www.outsystems.com© OutSystems – all rights reservedThe changing role of theEnterprise ArchitectNuno BaptistaExpert Services Managernuno.baptista@outsystems.comhttp://bit.ly/architectrolewww.outsystems.com
    2. 2. www.outsystems.com© OutSystems – all rights reservedGet to know itEA translates business vision andstrategy into effective enterprise changeWikipedia sourceEnterprise Architect ?
    3. 3. www.outsystems.com© OutSystems – all rights reservedGet to know itWhat is changing?• Strategic thinker• Business Oriented• Innovation driverMike Walker - Microsoft
    4. 4. www.outsystems.com© OutSystems – all rights reservedNew challenges of EA rolePromote IT-Business alignment#1Accelerate innovation#2Maximize investment returns#3Reduce costs#4
    5. 5. www.outsystems.com© OutSystems – all rights reserved• Understand your business• Prioritize your application portfolio#1 Promote IT andBusiness AlignmentDon’t fight the evil business!
    6. 6. www.outsystems.com© OutSystems – all rights reservedSupport the enterprise strategyManage a prioritized application portfolioMaximize the business value of ITStrategy & BudgetCorporate /IT ManagementDeliver and maintainIT OperationMeasureexpectations andbenefitsBusiness Operation#1 – IT & Business alignment
    7. 7. www.outsystems.com© OutSystems – all rights reserved• Adopt Pace Layered model– Flexible governance models– Try and Fail fast on the right layer#2 AcceleratinginnovationHolograms will become reality and change your way of communicate.
    8. 8. www.outsystems.com© OutSystems – all rights reserved#2 – Adopt Pace Layered model
    9. 9. www.outsystems.com© OutSystems – all rights reserved#2 – Try and Fail fast
    10. 10. www.outsystems.com© OutSystems – all rights reserved#2 – Try and Fail fastBuilt a prototype• Innovative idea• Delivery Effort 15 days• 3 months of experimentalphase• No performance tune• Planned new featuresAirport ticket validate systemToday• 24/7 in 5 airports• Mission critical for operationsupport• ~20K hits per day• Billing system integration• Partners notifications
    11. 11. www.outsystems.com© OutSystems – all rights reserved#2 – Try and Fail fastChallengeWhat is your innovative idea thatwill change your business this year?Golden rules:• Start small• Involve your business• Be fast to change and to fix• Evaluate the benefit and user adoption
    12. 12. www.outsystems.com© OutSystems – all rights reserved• Avoid becoming legacy– Design for Change#3 Maximizeinvestment returnsLucas first Star Wars film grossed $1.17 billion
    13. 13. www.outsystems.com© OutSystems – all rights reserved• Measure cost of maintenance• Build vs buy approach• Build with a technology that allows you to change easilySTANDARDDIFFERENTIATINGINNOVATING#3 - Don’t create new legacy
    14. 14. www.outsystems.com© OutSystems – all rights reserved#3 - Design for Change
    15. 15. www.outsystems.com© OutSystems – all rights reserved• Built in Non-Functional Requirements (NFRs)• Deliver fast• Change faster#4 Reduce CostsUsing OutSystems Platform™How much would a Death Star really cost?
    16. 16. www.outsystems.com© OutSystems – all rights reserved• Migrate DBMS from SQLServer 2005 to Oracle 11g.• Migrate OutSystems Platform from 5.1 to 7.0• Migrate physical hardware from 32 to 64bits in VMs.• Migrate Operating System to Windows Server 2008• Minimum downtime possible#4 – Built in NFRsStandardize and Update OutSystemsinfrastructure to recent systems.
    17. 17. www.outsystems.com© OutSystems – all rights reservedPerformantScalableDocumented AuditableMaintainable#4 – Built in NFRsPortable
    18. 18. www.outsystems.com© OutSystems – all rights reserved#4 – Deliver fast, change fasterDevelopmentModel driven developmentreduces time to buildIntegrations are simplifiedMaintenanceBuilt in dependency analysisNFRs support regardless ofchangeOperationsDeployment process isautomatedPerformance Managementbuilt in all applications
    19. 19. www.outsystems.com© OutSystems – all rights reservedNew challenges of EA rolePromote IT-Business alignmentUnderstand your business, Prioritize your applicationportfolio#1Accelerate innovationAdopt Pace Layered model#2Maximize investment returnsAvoid becoming legacy#3Reduce costsOutSystems Platform™ features#4
    20. 20. www.outsystems.com© OutSystems – all rights reserved
    21. 21. www.outsystems.com© OutSystems – all rights reservedThank you!Nuno BaptistaExpert Services Managernuno.baptista@outsystems.comhttp://bit.ly/architectrolewww.outsystems.com
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×