The agile manifesto speaks to the values and behaviours that enable people to work together, and enable them to respond to change effectively, in a dynamic and changing context. At the core of the manifesto, value is placed upon "individuals and interactions", "responding to change", "working software", and "customer collaboration".

What started as a healthy curiosity for the series "Aircrash Investigations" in my teenage years, over time progressed into me spending an inordinate amount of time binge-watching anything related to a discussion of air incidents and accidents. In the more recent years, as I have been watching more of the (many) videos, the parallels between how aviation professionals approach an incident to effectively aviate, and how we software development professionals approach effective software development, become more and more apparent.

In this session I'd like to take a few air incidents as case studies, along with certain examples from the projects I've been part of in the last 17 years of my tech career, and talk through the behaviours that enable pilots and software developers alike to respond to a changing context. Let's talk about human behaviours, leadership, and being on top of the ‘working-effectively-together-to-respond-to-change’ game!