35 min
Building resiliency through safeguarding - Llewellyn Falco For Agility's Sake
-
- Management
He's back! Tech Craftsmanship Coach Llewellyn Falco shares stories of his second visit to Amway. Some of the topics he touches on in this episode are:
Anti-fragile: a systemic way of implementing things so that when they break, you get stronger. More resilient. If your system is dependent on discipline, it’s broken.Safeguarding: after an issue was resolved, the team reflected on these 3 questions to help them build more resiliency for the future: What allowed us to create this situation?What made it hard for us to discover what it was?What made it hard to fix?PS: Don't start safeguarding in the middle of a crisis; wait until it's over (but not too long). Learning through documenting: As you document something, it prompts new ideas for how the thing could work. Shared, isolated, mutable and non-mutable states: the only combination to avoid is the one that everybody chooses = shared + mutable. What the team did when multi-threading threw a wrench in their testing…Continuous improvement: stop worrying about how to improve faster, worry about starting. Make improvement an everyday habit, and speed will come later.
He's back! Tech Craftsmanship Coach Llewellyn Falco shares stories of his second visit to Amway. Some of the topics he touches on in this episode are:
Anti-fragile: a systemic way of implementing things so that when they break, you get stronger. More resilient. If your system is dependent on discipline, it’s broken.Safeguarding: after an issue was resolved, the team reflected on these 3 questions to help them build more resiliency for the future: What allowed us to create this situation?What made it hard for us to discover what it was?What made it hard to fix?PS: Don't start safeguarding in the middle of a crisis; wait until it's over (but not too long). Learning through documenting: As you document something, it prompts new ideas for how the thing could work. Shared, isolated, mutable and non-mutable states: the only combination to avoid is the one that everybody chooses = shared + mutable. What the team did when multi-threading threw a wrench in their testing…Continuous improvement: stop worrying about how to improve faster, worry about starting. Make improvement an everyday habit, and speed will come later.
35 min