Description
In IT, resiliency is often interpreted in very narrow ways. The fixation is often on purely technical aspects. Whilst discussions around isolated failure planes, redundant provisoning, and self-healing systems can all be part and parcel of improving the resiliency of the systems we create, the focus on the purely technical means we are all too often ignoring critical aspects which are key to understand if we really want to deliver resiliency.
In this talk, Sam Newman will explore two models to help show how many factors come into play when addressing resilience. He will interpret David Woods "Four Concepts For Resilience", putting them into the context of the software systems we build to give you some practical advice about the changes you can make in your own organisations. He will also introduce the concept of socitechnical systems, to show the essential interconnection between the social and technical sides of software delivery.
