Systematic risk minimization through "iterative" organizational development
summary
Describes using 2- and 4-week Scrum-style sprints and iterative organizational development to reduce operational risks from unforeseen events (pandemics, staff loss, component deprecation, integration delays). It explains concrete practices: release- and sprint-goal planning, team backlogs, structured project control, formal technical decision points, integration points, and an MVP focus, which cut technical showstoppers from 10 to 2 over two years and improved releases, knowledge distribution, and adaptability to COVID.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:06Agile transformation motivation
- 3:13Medical Solutions complexity
- 6:02Agile development methods
- 8:11Cultural change feedback
- 10:18Project control evolution
- 13:49Project control visualization
- 17:23Decision-making and prioritization
- 20:15Prototyping challenges
- 21:58Dynamic roadmap releases
- 25:52MVP value focus
- 27:41Pandemic impact on control
- 29:03Agile benefits at scale
- 33:19Sustainable cultural change
- 34:24Q&A
related talks
40mAgile Software Development: Practice and Analytics
01h 13mScrum for Executives, Leaders, and Your Boss
38mIterative Threat Modelling: Security in Agile Development
21mAgile Delivery in an Uncertain Market
20mAgile development application for live ops
48mHow to Win and Start Contract Development Projects That Leverage Agile Values
21mScaled Agile DevOps
54mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World