Download as PDF, PPTX
Uploaded byIxchel Ruiz
Failure is not an option
The document discusses the challenges and realities of failure in IT and DevOps, citing research that highlights significant cost overruns in technology projects. It emphasizes the importance of recognizing different types of failures, including preventable and intelligent failures, which can lead to valuable learning opportunities. Additionally, it touches on the notion of psychological safety in organizations to foster a conducive environment for learning from failures.
Failure is not an option
- 1. DevOps Days Denmark2023 Failure is not an Option Ixchel Ruiz, JFrog
- 2. DevOps Days Denmark2023 Failure is not an Option It’s a Fact Ixchel Ruiz, JFrog
- 5. Me “HUMAN writing codefor HUMANS to improve HUMAN life”
- 6. Agent Smith —Matrix “Never send a HUMAN to do a MACHINE’S job ”
- 7.
- 16.
- 18. We should aimfor perfection Jon Bowers
- 19. The unexpected bene f it of celebratingfailure Astro Teller
- 20.
- 21. Why Your ITProject May Be Riskier Than You Think Bent Flyvbjerg and Alexander Budzier 2011
- 22. Bent Flyvbjerg andAlexander Budzier New research shows surprisingly high numbers of out-of-control tech projects—ones that can sink entire companies and careers.
- 23. IT change initiatives It’sthat an unusually large proportion of IT change initiatives incur massive overages.
- 24. “Fully 1 in6 of the projects was a black swan, with a cost overrun of 200%. On average, a schedule overrun of almost 70%”
- 25. The Empirical Reality ofIT Project Cost Overruns: Discovering A Power- Law Distribution Bent Flyvbjerg and Alexander Budzier 2022
- 26. Bent Flyvbjerg andAlexander Budzier Disastrous IT projects are not the outliers they are sometimes interpreted
- 27. Bent Flyvbjerg andAlexander Budzier The key point that can be drawn here is that substantial overruns in IT projects may result from interdependencies.
- 28. A closer look Failurein “IT”
- 29.
- 31.
- 32.
- 33. In-Depth Analysis ofOpen Source Security Vulnerabilities Most Impactful to DevOps and DevSecOps Teams 2023 JFrog Security Research Report
- 34. 2023 JFrog SecurityResearch Report “The majority of vulnerabilities detailed in this report were not as easy to exploit”
- 35. 2023 JFrog SecurityResearch Report “Many of them required complex con f iguration scenarios or speci f ic conditions under which an attack could be successfully executed.”
- 36. 2023 JFrog SecurityResearch Report “Considering the context in which software is deployed and utilized when evaluating the impact of any CVE.”
- 37.
- 39. The Failure Issue HarvardBusiness Review April 2011
- 40.
- 41. Not all failuresare created equally
- 42.
- 43.
- 44. Preventable failures “ Mostfailures in this category can indeed be considered “bad” They usually involve deviations from speci f ications in the closely de f ined processes of high-volume or routine operations in manufacturing and services “
- 45.
- 46.
- 47. Complexity-related “ A largenumber of organisational failures are due to the inherent uncertainty of work: A particular combination of needs, people, and problems may have never occurred before ”
- 48.
- 49. Intelligent “Failures in thiscategory can rightly be considered “good,” because they provide valuable new knowledge that can help an organization leap ahead of the competition and ensure its future growth”
- 50.
- 51. How failure size affectslearning in innovation DRUID15
- 52. Process “Failure identi f ication, Failureanalysis, and deliberate experimentation."
- 53. Failure identi fi cation “Recognising smallfailures from a complex system”
- 54. Failure analysis “Process ofunderstanding the cause of the failure and extracting lessons to avoid future failure”
- 55. Deliberate experiment “Design solutionexperiments to experience failure early in a safe and controlled setting.”
- 56. How fast welearn
- 57. The tipping pointbetween Failure and Success
- 58. The tipping pointbetween Failure and Success
- 59. The Tipping Point BetweenFailure and Success Yian Yin and Yang Wang
- 60. Below the tippingpoint : stagnation region Not learning enough to actually achieve success.
- 61. Above the tippingpoint People fail over and over but they get to fail faster and faster to eventually approach success.
- 62. Increase the returnon failure
- 63. Increase your return onFailure Julian Birkinshaw and Martine Haas
- 64. Increase return Steps Learn fromevery Failure Share the lessons Review your pattern of failure
- 65. Psychological Safety, Trust, andLearning in Organizations: A Group-level Lens Amy C. Edmondson
- 66. Psychological safety A climatein which people are comfortable being (and expressing) themselves.
- 67. Coming back Failure in“DevOps”
- 68.
- 70.
- 73. JFrog Artifactory: Thedatabase of DevOps Single source of truth Consolidate & Enhance data Distribute Knowledge Security Best practices Curation