1 / 59

Galls lov og erstatningsprosjekter Johannes Brodwall Chief scientist, Steria

Galls lov og erstatningsprosjekter Johannes Brodwall Chief scientist, Steria. "If A System Is Working, Leave It Alone. Don't Change Anything!". Planen. “Systemet må erstattes!”. Leverandøren gir ikke support. Vi får ikke tak i kompetanse. Kompleksitet ødelegger vedlikeholdbarhet.

Download Presentation

Galls lov og erstatningsprosjekter Johannes Brodwall Chief scientist, Steria

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Galls lov og erstatningsprosjekter Johannes Brodwall Chief scientist, Steria

  2. "If A System Is Working, Leave It Alone. Don't Change Anything!"

  3. Planen

  4. “Systemet må erstattes!”

  5. Leverandøren gir ikke support

  6. Vi får ikke tak i kompetanse

  7. Kompleksitet ødelegger vedlikeholdbarhet

  8. “Bygg et nytt system!”

  9. Dagens system er kravspec

  10. Estimert kostnad:85 411 timeverk

  11. (Cirka 2 livsverk)

  12. “Ikke invester i dagens system”

  13. Alt erstattes under ett

  14. Nytt system,gammel tjeneste

  15. Uortodoks observasjon #1: Det finnes billigere måter å holde liv i gammel forretningsmodell

  16. "A Complex System Designed From Scratch Never Works And Cannot Be Made To Work. You Have To Start Over, Beginning With A Working Simple System"

  17. Det finnes bedre grunner!

  18. Virkeligheten

  19. “Forsinket”

  20. “Sparket”

  21. “Vis at investeringen er verdt noe!”

  22. Produksjonsetter noe

  23. Uortodoks observasjon #2: Nytt og gammelt system vil leve sammen

  24. ... veldig gode nyheter

  25. Gradvis erstatning http://www.flickr.com/photos/wolf_359/190195652/

  26. Tekniske patterns http://www.flickr.com/photos/wolf_359/190195652/

  27. Delt database

  28. Import/eksport

  29. Datatjenestelag

  30. Parallell produksjon

  31. Krav patterns http://www.flickr.com/photos/wolf_359/190195652/

  32. Risiko

  33. Kostnad

  34. Isolert brukeregruppe

  35. Ny brukeregruppe

  36. Arkitektur http://www.flickr.com/photos/wolf_359/190195652/

  37. "...organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations." - Conway's Law http://www.flickr.com/photos/wolf_359/190195652/

  38. Uortodoks observasjon #3: I store prosjekter er organisering den viktigste faktoren for arkitekturen

  39. Hvor mange personer i et team? http://www.flickr.com/photos/wolf_359/190195652/

  40. 2-pizza-team http://www.flickr.com/photos/wolf_359/190195652/

  41. 10 personer med felles kodebase http://www.flickr.com/photos/wolf_359/190195652/

  42. 30 personer med integrert kodebase http://www.flickr.com/photos/wolf_359/190195652/

  43. Grensen for kontinuerlig integrasjon http://www.flickr.com/photos/wolf_359/190195652/

  44. Versjonering hindrer endring http://www.flickr.com/photos/wolf_359/190195652/

  45. Hvis jeg var sjef http://flickr.com/photos/oh_simone/2800426735/

  46. Team #1: Risiko http://flickr.com/photos/oh_simone/2800426735/

  47. Team #2: Effektivisering http://flickr.com/photos/oh_simone/2800426735/

  48. Team #3: Isolert brukergruppe http://flickr.com/photos/oh_simone/2800426735/

  49. Team #4: Portal http://flickr.com/photos/oh_simone/2800426735/

  50. Retningslinjer http://flickr.com/photos/oh_simone/2800426735/

More Related