This event raised important questions about system resilience, response times, and organisational preparedness. Global organisations can learn lessons from this incident and ensure they are aligned with agile principles, particularly around organisational change, risk management, and adaptability.
To understand the broader implications of this outage, we can draw a familiar comparison with something like a mission control launch failure. Space agencies like NASA, which uses the Scrum agile methodology to develop software for projects like the Space Launch System (SLS), regularly deal with incredibly high stakes during rocket launches, where split-second decisions and cross-functional collaboration can mean the difference between success and failure. These ambitious launch projects involve numerous complex components, teams and stakeholders, making interdepartmental collaboration crucial.
In mission control, engineers and mission managers face the highest level of pressure when systems fail, but their response isn't based on panic. Instead, it's grounded in agile principles that prioritise rapid iteration, collaboration, and the ability to adapt to new information. NASA uses SCRUM with its iterative feedback loops, transparent communication, and failover systems to ensure that if something goes wrong, there's a path forward. Could these agile practices have made a difference with CrowdStrike?