espen opedal
TRANSCRIPT
EA 2015 - Business and IT Alignment.Onsdag den 4. november 2015
Alignment af Business and ITEspen Opedal, CIO, TRYG
Agenda
May 1, 20233
1. Tryg og Tryg IT
2. EA og kontaktflade til Forretning
3. Ny model for mere rettidig brug af ny teknologi
4. Enkel checkliste for styring af IT Arkitekturen
5. Øget involvering af partnere
7
1.4 One Key-challenge : Complexity
November 2014
Business complexity
IT-complexity
Geographical setup
Consequences• Operational instability• Reduced time to market• Increased development
and test costs• Complex competence
mapping• High software costs
Actions• Decrease business
complexity• Reduce IT complexity• Long term IT-strategy• Sourcing• Select domain specific
vendors
1.5 Working with Architecture Domains
Used for• Classification of
solutions• Selection of focus areas• Selection of vendors
and partners• TCO, and much more
2.1 Ny Enterprise Architecture placering
• Fra stabsfunktion til linje organisation, og nu i frontlinjen. • Enterprise arkitekter er aktive deltagere i initiering af projektet.• CIO og EA Direktør holder BRM–møder og Road shows, sammen • Tryg IT har Enterprise Architects – vores partnere har Solution Architects
som inddrages tidligt i forløbet.
Plan Build Run
CIOGov
EA
Plan Build Run
CIO
EA
OLD NEW
2.2 Tryg IT organisation pr. May 2015
May 1, 202310
BUILD
CORE
RUNPLAN
CIO
SLM & T2PBus. support mgmt. (incl. support)
InitiationPeter Appelros
Development Team 1 DK (incl. ODC)
Global delivery
System Mgmt. NO End User Services
IT OperationsJeroen Bik
Web & Bibeln
Architecture
Test Mgmt. + Method
BFOJens Bjørnebo
Core SystemsAsim Hameed
System Mgmt. DK
Development Management
Project DeliveryNiels Vorum-Petersen
Development Team 2 DK (incl. ODC)
Development Team 1 NO (incl. ODC)
Development Team 2 NO (incl. ODC)
Winsure
Business Development and Projects
Core Systems NOMorten Storetvedt
Core Systems SEEmma Kindblom
IT Vendor relations
Project Mgmt. + Business Analysis
Level 2 director
Level 3 manager Group
November 201412
A more agile approach to quickly maximize business opportunities
•Let the business try, let them be the driver (pull)•‘Fail faster’•Beta approach/Quick wins/Agile•Solve problems as they come•Changing plans, no fixed end date
3. Men, vi afviger også fra vores modeller
Some projects require a development ‘modus 2’
Building Foundation (Structure):• License set-up• Network capacity• Infrastructure• Cloud set-up etc
4. EA Check-List for Project Managers and Architects
• Have we evaluated to reuse what we already have; solutions, vendors and platforms (80% is good enough)? One solution per business capability, reducing overlapping solutions
• Have we chosen a market standard solution and will we keep it standard? We want proven solutions, not to be "first mover” in new technologies
• ”One solution in, One or more out” – Will any new solution decommission old ones? We want to continuously reduce complexity to promote IT stability, reduce cost and build a stable architecture
• Do we understand Business & IT impact clearly before we start?
• Does the solution promote STP, Digitalisation and Self-Service etc?
• Have we evaluated architecture guidelines, technical capacity, integration needs etc?
• Will the solution promote customer/user experience, one source for key data
• Have any deviations to the above been correctly approved?
IT Architectural Check-List (high level)
5.1 Utilize partnerships and competition
Projects
AD
AM
Operations
Coreapplications
Sharedapplications
5.2 Sourcing Partnerships - does the happy marriage exist ?
•Monogami or polygami
•Partner or Supplier
•Balancing trust and strict follow up
•Dependencies and committment
•We’re in it together, it’s a win-win or lose-lose game
•Open organisational relationship or exclusive club
•The importance of documenting benefit realisation
•Keep up the internal change management