Legacy is sexy and this room is hot

Transcription

1 Legacy is sexy and this room is hot Story Drivers Tips Agile / Scrum Solution SOA / Integration Coaching Quality Enterprise Java 1

2 Why this talk? Remove from tech dictionary words: generic reusable flexible 2

3 Large software projects today...are replacing something old for new. Many of them have single goal: Replace outdated technology with new one. Many of them are huge investments with long term promises of so called flexibility in future....and if your project is not one of these, then you re maybe creating a christmas tree. Looks nice, but it is dead very soon. 3

4 4

5 5

6 6

7 Great Mosque of Djenné, Mali ruins

8 Great Mosque of Djenné rebuilt

9 Great Mosque of Djenné

10 10

11 11

12 12

13 13

14 14

15 15

16 Everyone is involved 16

17 17

18 About 6 years ago... 24/7 system for traffic management, transport, environmental safety and crisis management. Port of Rotterdam, Project HaMIS 1. Replace outdated traffic management system 2. Support the port of Rotterdam expansion 18

19 Old IVS Expert TARGET Bunkeren REF NOD Passage Morsingen RCS SPIL DataDirk SSN KRVE systeem VKL VKB GSA GSE REF QORRIDOR DHK ZOS DWH SAP ZORRO Identity Vault MARS RWS schepentabel Infoschermen HCC VOS RostarFlex Port Security Bedr. DB Journaal B&S Journaal TMV Journaal PVT Journaal VPO Journaal VTS RIV PCS TAM SRV HM SISTER Dossier Mini BOS KLPD systeem WM NNI Legenda naam te vervangen applicatie naam externe applicatie interface via DOD-Port naam uitgefaseerde applicatie uitgefaseerde interface naam niet te vervangen applicatie directe interface (01) (02) (03) (04) (05) (06) (07) (08) (09) (10) (11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25) (26) (27) (28) (29) (30) (31) (32) (33) (34) (36) (35) (37) (38) 19

20 New (as defined about 5 years ago) 20

21 Lots of documents Operations Vision Architecture Vision Blueprint QA Vision Reference data Vision... Migration Plan 21

22 We just need identified use cases Project Start Architecture Q&A department Architecture with 4 layers & 6 subsystems BPEL process server 6 architects RUP and Scrum but 800+ architectural decisions 22

23 1 Use Case in 6 months 23

24 (Re)Started Ship inspections process Little risk Significant business value Migration stuff completely postponed Agile / Scrum introduction One sprint later, useful functions delivered in production 24

25 25

26 Welcome to double legacy! 26

27 Any decision that can be postponed is postponed...also the migration path 27

28 Which path to choose? Should we do all reporting first in the new system? Which part of the system should we replace first? How do we prevent a big bang? Where to start? We followed ships in harbour! 28

29 Migration without a plan Messaging???? User???? Messaging???????? IVS (old) HaMIS (new) Messaging BVDM Messaging 29

30 Migration = Strangulation 24/7 system Every 2 weeks in production User Business event 2 Business event 1 IVS (old) Business event 1 Business event 2 HaMIS (new) data not yet managed in HaMIS "The most important reason to consider a strangler application over a cut-over rewrite is reduced risk. - Martin Fowler, StranglerApplication 30

31 We banned term: Generic or Reusable on every level 31

32 Aren t you creating a mess? One team delivers the simplest possible solution Another team delivers another similar even simpler possible solution :-)...and maybe third one. Then, we get together and talk about what you learned and which one is really the best in this context. 32

33 Example portview portmap Features VesselPosition Startmal some fat library MapStyle ImageLayer GIS server HaMIS backend GIS server 33

34 Delivering value with partial foundation or DVWPF :-) 34

35 Examples Data model with production data is gradually extended and continually refactored IBM Websphere replaced by JBoss User interface redesigned 2 or more times SOAP replaced by binary Hessian Core domain model concepts (gradually) redesigned: inspection checklist, vessel visit vs. vessel 35

36 36

37 Each team is a crossfunctional team and has intensive contact with end-users 37

38 Some challenges Teams want to understand business first, before accepting epics and stories. Continuous discussion about priorities Making business value SMART. Technical complexity is NOT a real challenge. Should we spend (or waste) money on synchronization vs. postpone going live. 38

39 65 sprints later; Almost all of them delivered business value (functions in production) 39

40 Software Quality Agile (Fowler)?? 40

41 Lessons learned Never stop delivering business value. Deal with migration gradually / strangulation Everything in software can be soft even data / domain model! Trust in business / context driven approach above standard / generic solutions Involve everyone to solve complex problems 41

42 Software Agile quality Scrum Business DevOps events Liquid architecture User domain Context 42

43 Thank You! You work in Hong Kong? Please contact 43