The client (US Air Force) is trying to adopt and move towards and agile approach to aircraft worthiness. They would like to speak to a peer who has knowledge of the commercial airlines agile processes. Specifically, how are aircraft and or commercial airlines conducting agile practices while implementing safety constraints into their agile processes? How do large organizations like commercial airlines with safety constraints adopt safety into their agile processes? What are some considerations, advice and approaches to help complex processes with safety constraints still adopt agile in order to become more efficient.
Sort By:
Oldest
EMEA IT Service Management Manager in Miscellaneous3 months ago
I reckon it would be that Safety takes top priority and should be marked as such in the backlog, so that when it comes to implementation, this work is done first.Senior Manager in Softwarea month ago
This takes me back to when I was getting my Agile certifications, and I often found myself thinking about these kinds of scenarios. In commercial aviation, one of the big things they do is use iterative development cycles, which are a lot like agile sprints. This approach lets teams make quick adjustments based on feedback, and that’s really important for making sure safety is built into the process from the get-go. They usually put together cross-functional teams that include not just engineers, but also safety experts and compliance people. This way, everyone is aligned and understands that safety is the top priority throughout the whole development process.Now, when we talk about safety, it’s really essential to make it a core value in agile practices. They often use risk assessment tools like Failure Mode and Effects Analysis (FMEA) to identify potential safety issues early on. This proactive approach really pays off in the long run.
Another important aspect is fostering a culture that prioritizes safety. Training programs that highlight this can help everyone see how to balance the need for being agile with the strict safety requirements they have to follow. Plus, starting with small, incremental changes instead of going for big overhauls can help reduce risks while still moving things forward.