Failure is not an option
•
0 likes•15 views
Failure is an inevitable part of success. Failure in the context of innovation efforts has helped thousands of start-up companies to succeed but in the context of a known execution process, it can harm results or reputations or create undue risk. In software development we are situated at the cross road between innovation and known processes so how do we benefit from failure and achieve success? In this session we will explore several studies and best practices of successful companies that have embraced them both.
Recommended
Recommended
More Related Content
Similar to Failure is not an option
Similar to Failure is not an option (20)
More from Ixchel Ruiz
More from Ixchel Ruiz (10)
Recently uploaded
Recently uploaded (20)
Failure is not an option
- 1. DevOps Days Denmark 2023 Failure is not an Option Ixchel Ruiz, JFrog
- 2. DevOps Days Denmark 2023 Failure is not an Option It’s a Fact Ixchel Ruiz, JFrog
- 5. Me “HUMAN writing code for HUMANS to improve HUMAN life”
- 6. Agent Smith — Matrix “Never send a HUMAN to do a MACHINE’S job ”
- 7. Failure
- 18. We should aim for perfection Jon Bowers
- 19. The unexpected bene f it of celebrating failure Astro Teller
- 20. Project Level Failure in “IT”
- 21. Why Your IT Project May Be Riskier Than You Think Bent Flyvbjerg and Alexander Budzier 2011
- 22. Bent Flyvbjerg and Alexander 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’s that an unusually large proportion of IT change initiatives incur massive overages.
- 24. “Fully 1 in 6 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 of IT Project Cost Overruns: Discovering A Power- Law Distribution Bent Flyvbjerg and Alexander Budzier 2022
- 26. Bent Flyvbjerg and Alexander Budzier Disastrous IT projects are not the outliers they are sometimes interpreted
- 27. Bent Flyvbjerg and Alexander Budzier The key point that can be drawn here is that substantial overruns in IT projects may result from interdependencies.
- 28. A closer look Failure in “IT”
- 29. Testing
- 32. Security
- 33. In-Depth Analysis of Open Source Security Vulnerabilities Most Impactful to DevOps and DevSecOps Teams 2023 JFrog Security Research Report
- 34. 2023 JFrog Security Research Report “The majority of vulnerabilities detailed in this report were not as easy to exploit”
- 35. 2023 JFrog Security Research 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 Security Research Report “Considering the context in which software is deployed and utilized when evaluating the impact of any CVE.”
- 39. The Failure Issue Harvard Business Review April 2011
- 41. Not all failures are created equally
- 43. Preventable
- 44. Preventable failures “ Most failures 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. “MACHINE’S job ”
- 47. Complexity-related “ A large number 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. Intelligent
- 49. Intelligent “Failures in this category 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. Learning Process
- 51. How failure size affects learning in innovation DRUID15
- 52. Process “Failure identi f ication, Failure analysis, and deliberate experimentation."
- 53. Failure identi fi cation “Recognising small failures from a complex system”
- 54. Failure analysis “Process of understanding the cause of the failure and extracting lessons to avoid future failure”
- 55. Deliberate experiment “Design solution experiments to experience failure early in a safe and controlled setting.”
- 56. How fast we learn
- 57. The tipping point between Failure and Success
- 58. The tipping point between Failure and Success
- 59. The Tipping Point Between Failure and Success Yian Yin and Yang Wang
- 60. Below the tipping point : stagnation region Not learning enough to actually achieve success.
- 61. Above the tipping point People fail over and over but they get to fail faster and faster to eventually approach success.
- 62. Increase the return on failure
- 63. Increase your return on Failure Julian Birkinshaw and Martine Haas
- 64. Increase return Steps Learn from every Failure Share the lessons Review your pattern of failure
- 65. Psychological Safety, Trust, and Learning in Organizations: A Group-level Lens Amy C. Edmondson
- 66. Psychological safety A climate in which people are comfortable being (and expressing) themselves.
- 67. Coming back Failure in “DevOps”
- 68. SDLC
- 73. JFrog Artifactory: The database of DevOps Single source of truth Consolidate & Enhance data Distribute Knowledge Security Best practices Curation