![#DOAW20
DevOps and its resulting technical, architectural, and cultural
practices represent a convergence of many philosophical and
management movements
DevOps is the outcome of applying the most trusted principles
from the domain of physical manufacturing and leadership to the IT
value stream.
[…. ]many also view DevOps as the logical continuation of the Agile
software journey that began in 2001
(The DevOps Handbook)
DEVOPS IS…](https://image.slidesharecdn.com/presentazione-200116142657/85/Un-Viaggio-Verso-DevOps-5-320.jpg)
Un Viaggio Verso DevOps
- 1. UN VIAGGIO VERSO DEVOPS Daniele Pozzobon @pozzobondaniele dnl.pozzobon@gmail.com
- 3. #DOAW20 Who has DevOps culture? Who is transitioning? Who lost hope? WHAT’SDEVOPS?
- 4. #DOAW20 A set of practices intended to reduce the time between committing a change to a system and the change being placed into normal production, while ensuring high quality (wikipedia.en) WHAT’SDEVOPS?
- 5. #DOAW20 DevOps and its resulting technical, architectural, and cultural practices represent a convergence of many philosophical and management movements DevOps is the outcome of applying the most trusted principles from the domain of physical manufacturing and leadership to the IT value stream. […. ]many also view DevOps as the logical continuation of the Agile software journey that began in 2001 (The DevOps Handbook) DEVOPS IS…
- 6. #DOAW20 DevOps is the result of applying Lean principles to the technology value stream (The DevOps Handbook) DEVOPS IS…
- 8. #DOAW20 THETHREEWAYS Set of principles Principles of Flow Principles of Feedback Principles of Continual Learning and Experimentation
- 10. #DOAW20 THEFIRSTWAY Delivering value to the customers at steady pace Make your work Visible Limit Work in progress Reduce batch sizes Reduce the number of handoffs Continually identify and elevate your constraints Eliminate hardships and waste in the value stream
- 11. #DOAW20 THESECONDWAY Course correction and learnings based on feedback See problems as they occur Swarm and solve problems to build new knowledge Keep pushing quality closer to the source Enable optimizing for downstream work centers
- 12. #DOAW20 THETHIRDWAY Learn, Grow and Improve over time Enabling organizational learning and a safety culture Institutionalize the improvement of daily work Transform local discoveries into global improvements Inject resilience patterns into our daily work Leaders reinforce a learning culture
- 13. #DOAW20 THETHREEWAYS–SKILLCHART Make your work Visible Limit Work in progress Reduce batch sizes Reduce the number of handoffs Continually identify and elevate your constraints Eliminate hardships and waste in the value stream Working safely within complex systems See problems as they occur Swarm and solve problems to build new knowledge Keep pushing quality closer to the source Enable optimizing for downstream work centers Enabling organizational learning and a safety culture Instituzionalize the improvement of daily work Transform local discoveries into global improvements Inject resilience patterns into our daily work Leaders reinforce a learning culture Fake Company
- 14. #DOAW20 WHO ARE WE TALKING ABOUT?
- 15. #DOAW20 MODINE
- 16. #DOAW20 ONE AND A HALF YEARS AGO…
- 17. #DOAW20 VERSIONCONTROL Vault from Source Gear Dated technology Centralized Difficult to integrate Problems during normal operation
- 18. #DOAW20 REQUIREMENTSANDBUGSHANDLING From Trello to Jira Recently migrated to Jira Beginning to use Kanban No use of Jira’s analytics Start proper reporting
- 19. #DOAW20 RELEASEMANAGEMENT Partial automation Partly by hand Part scripted Risky and Slow
- 20. #DOAW20 CODESTATUS Old Code Procedural Low Quality New Code Low Quality from Contractor Good Quality from Team Tests No Tests
- 21. #DOAW20 RELATIONSHIPWITHIT Complicated Plus side Almost complete control over all flow Collaborative Negative side Bureaucratic Slow reaction to our requests
- 22. #DOAW20 MODINE AND THE THREE WAYS BACK THEN
- 23. #DOAW20 THEFIRSTWAY Eliminate hardships and waste in the value stream Continually identify and elevate your constraints Reduce the number of handoffs Reduce batch sizes Limit Work in progress Make your work Visible Principles of Flow
- 24. #DOAW20 THESECONDWAY Enable optimizing for downstream work centers Keep pushing quality closer to the source Swarm and solve problems to build new knowledge See problems as they occur Principles of Feedback
- 25. #DOAW20 THETHIRDWAY Leaders reinforce a learning culture Inject resilience patterns into our daily work Transform local discoveries into global improvements Instituzionalize the improvement of daily work Enabling organizational learning and a safety culture Principles of Learning and Experimentation
- 27. #DOAW20 CODELIFECYCLE Source Control Management One of the biggest roadblocks Modern technology Needed Technologies analyzed SVN Git TFS Decided for Git Better integration More flexibility
- 28. #DOAW20 CODELIFECYCLE Migration strategy Clean History Partial History All History How to choose https://bit.ly/32PqF89 Search XXX to Git
- 29. #DOAW20 CODELIFECYCLE Where to Host Code Custom Central Repo BitBucket Azure DevOps Services Selection criteria Easy of use Integration with other Tools Future development
- 30. #DOAW20 DEPLOYMENTAUTOMATION Azure DevOps Pipelines Powerful Easy of use Build pipeline Hosted Quick Release pipeline On-premise Should be easy but…
- 31. #DOAW20 DEPLOYMENTAUTOMATION Where to start? https://bit.ly/2WfBeP0 https://dev.azure.com
- 32. #DOAW20 TESTS The problem with Tests Always left for later CI inefficient without tests Pilot project Unit Tests UI Tests Adopting UI Tests across the board More Visual Easier to “sell” Easier on brownfield
- 33. #DOAW20 TESTS Where to start? Start! Don’t Ask Gherkin (Specflow, Cucumber) Slowly Automate Sell the concept with patience Given I am logged in as an 'Administrator' When I have clicked on the User Management tab Then A table listing the current users is displayed
- 34. #DOAW20 SECURITY The problem with Security Always left for later • Started collaborating with Sec Team Dev team Simple security checks with Static Code Analysis Dependency Vulnerability checks OWASP ZAP Sec Team More in depth pen test
- 35. #DOAW20 SECURITY Where to start? OWASP Top Ten OWASP Developer Guide OWASP Zed Attack Proxy OWASP Wealth of Information and tools Dependecy Checker and RetireJS Static Code Analysis
- 36. #DOAW20 PROJECTMANAGEMENT Support Jira Better suited for handling support Improving reporting policy Improving Analytics New Projects Azure DevOps Boards Better suited for managing Agile projects
- 37. #DOAW20 OTHER ACTIONS Team sessions for improvement actions Cloud development
- 38. #DOAW20 MODINE AND THE THREE WAYS NOW
- 39. #DOAW20 THEFIRSTWAY Eliminate hardships and waste in the value stream Continually identify and elevate your constraints Reduce the number of handoffs Reduce batch sizes Limit Work in progress Make your work Visible Principles of Flow
- 40. #DOAW20 THESECONDWAY Enable optimizing for downstream work centers Keep pushing quality closer to the source Swarm and solve problems to build new knowledge See problems as they occur Working safely within complex systems Principles of Feedback
- 41. #DOAW20 THETHIRDWAY Leaders reinforce a learning culture Inject resilience patterns into our daily work Transform local discoveries into global improvements Instituzionalize the improvement of daily work Enabling organizational learning and a safety culture Principles of Continuous Learning
- 42. #DOAW20 WRAPPINGUP… Clear improvement Work on The Three Ways Flow Feedback Learning
Editor's Notes
- #3: Prima di cominciare dovuto rigraziamento agli sponsor senza I quali questo evento non sarebbe stato possibile
- #16: Produttori di Scambiatori di Calore 7000+ Lavoratori 30+ Fabbriche/Uffici Cresciuta acquisendo altre aziende Molta frammentazione
- #17: Quando sono arrivato io un anno e mezzo fa le azioni di miglioramento erano già iniziate e visto il terreno fertile è stato possibile attuare molte novità e migliorie in questo periodo. Ma, come eravamo messi un anno e mezzo fa?
- #21: (someone else code is always ugly) Lot’s of old code Heavy refactoring needed but not justified Good quality code by internal team Good abstractions Good composiblity Good reuse Low quality code by external contractor Lot’s of duplicate code Custom UI frameworks Poor abstractions Refactoring needed No Tests no test automation no test specifications no regression test all tests done by hand
- #22: (someone else code is always ugly) Lot’s of old code Heavy refactoring needed but not justified Good quality code by internal team Good abstractions Good composiblity Good reuse Low quality code by external contractor Lot’s of duplicate code Custom UI frameworks Poor abstractions Refactoring needed No Tests no test automation no test specifications no regression test all tests done by hand
- #23: Quando sono arrivato io un anno e mezzo fa le azioni di miglioramento erano già iniziate e visto il terreno fertile è stato possibile attuare molte novità e migliorie in questo periodo. Ma, come eravamo messi un anno e mezzo fa?
- #24: The First Way: si tratta di una serie di principi per massimizzare il flusso di valore dal nascita della necessita da parte del cliente alla soddisfazione della stessa attraverso nuove funzionalità. Principalemente abbiamo: Make your work Visible Limit Work in progress Reduce batch sizes Reduce the number of handoffs Continually identify and elevate your constraints Eliminate hardships and waste in the value stream
- #25: The second way: un gruppo di principi atti a migliorare il feedback Working safely within complex systems See problems as they occur Swarm and solve problems to build new knowledge Keep pushing quality closer to the source Enable optimizing for downstream work centers
- #26: The third way: questi invece sono un gruppo di principi che trattano l'apprendimento continuo e la sperimentazione Enabling organizational learning and a safety culture Instituzionalize the improvement of daily work Transform local discoveries into global improvements Inject resilience patterns into our daily work Leaders reinforce a learning culture
- #27: Quando sono arrivato io un anno e mezzo fa le azioni di miglioramento erano già iniziate e visto il terreno fertile è stato possibile attuare molte novità e migliorie in questo periodo. Ma, come eravamo messi un anno e mezzo fa?
- #28: (someone else code is always ugly) Lot’s of old code Heavy refactoring needed but not justified Good quality code by internal team Good abstractions Good composiblity Good reuse Low quality code by external contractor Lot’s of duplicate code Custom UI frameworks Poor abstractions Refactoring needed No Tests no test automation no test specifications no regression test all tests done by hand
- #29: https://www.youtube.com/watch?v=ULvb6kdrYHE
- #30: https://www.youtube.com/watch?v=ULvb6kdrYHE
- #31: (someone else code is always ugly) Lot’s of old code Heavy refactoring needed but not justified Good quality code by internal team Good abstractions Good composiblity Good reuse Low quality code by external contractor Lot’s of duplicate code Custom UI frameworks Poor abstractions Refactoring needed No Tests no test automation no test specifications no regression test all tests done by hand
- #32: (someone else code is always ugly) Lot’s of old code Heavy refactoring needed but not justified Good quality code by internal team Good abstractions Good composiblity Good reuse Low quality code by external contractor Lot’s of duplicate code Custom UI frameworks Poor abstractions Refactoring needed No Tests no test automation no test specifications no regression test all tests done by hand
- #33: (someone else code is always ugly) Lot’s of old code Heavy refactoring needed but not justified Good quality code by internal team Good abstractions Good composiblity Good reuse Low quality code by external contractor Lot’s of duplicate code Custom UI frameworks Poor abstractions Refactoring needed No Tests no test automation no test specifications no regression test all tests done by hand
- #34: (someone else code is always ugly) Lot’s of old code Heavy refactoring needed but not justified Good quality code by internal team Good abstractions Good composiblity Good reuse Low quality code by external contractor Lot’s of duplicate code Custom UI frameworks Poor abstractions Refactoring needed No Tests no test automation no test specifications no regression test all tests done by hand
- #35: (someone else code is always ugly) Lot’s of old code Heavy refactoring needed but not justified Good quality code by internal team Good abstractions Good composiblity Good reuse Low quality code by external contractor Lot’s of duplicate code Custom UI frameworks Poor abstractions Refactoring needed No Tests no test automation no test specifications no regression test all tests done by hand
- #36: (someone else code is always ugly) Lot’s of old code Heavy refactoring needed but not justified Good quality code by internal team Good abstractions Good composiblity Good reuse Low quality code by external contractor Lot’s of duplicate code Custom UI frameworks Poor abstractions Refactoring needed No Tests no test automation no test specifications no regression test all tests done by hand
- #37: (someone else code is always ugly) Lot’s of old code Heavy refactoring needed but not justified Good quality code by internal team Good abstractions Good composiblity Good reuse Low quality code by external contractor Lot’s of duplicate code Custom UI frameworks Poor abstractions Refactoring needed No Tests no test automation no test specifications no regression test all tests done by hand
- #38: (someone else code is always ugly) Lot’s of old code Heavy refactoring needed but not justified Good quality code by internal team Good abstractions Good composiblity Good reuse Low quality code by external contractor Lot’s of duplicate code Custom UI frameworks Poor abstractions Refactoring needed No Tests no test automation no test specifications no regression test all tests done by hand
- #39: Quando sono arrivato io un anno e mezzo fa le azioni di miglioramento erano già iniziate e visto il terreno fertile è stato possibile attuare molte novità e migliorie in questo periodo. Ma, come eravamo messi un anno e mezzo fa?
- #40: The First Way: si tratta di una serie di principi per massimizzare il flusso di valore dal nascita della necessita da parte del cliente alla soddisfazione della stessa attraverso nuove funzionalità. Principalemente abbiamo: Make your work Visible Limit Work in progress Reduce batch sizes Reduce the number of handoffs Continually identify and elevate your constraints Eliminate hardships and waste in the value stream
- #41: The second way: un gruppo di principi atti a migliorare il feedback Working safely within complex systems See problems as they occur Swarm and solve problems to build new knowledge Keep pushing quality closer to the source Enable optimizing for downstream work centers
- #42: The third way: questi invece sono un gruppo di principi che trattano l'apprendimento continuo e la sperimentazione Enabling organizational learning and a safety culture Instituzionalize the improvement of daily work Transform local discoveries into global improvements Inject resilience patterns into our daily work Leaders reinforce a learning culture
- #43: The third way: questi invece sono un gruppo di principi che trattano l'apprendimento continuo e la sperimentazione Enabling organizational learning and a safety culture Instituzionalize the improvement of daily work Transform local discoveries into global improvements Inject resilience patterns into our daily work Leaders reinforce a learning culture