What Aircrews Can Teach Testing Teams
United Flight 232 should have crashed with all 296 lives lost. Asiana Flight 214 should not have crashed at all. But the reality is very different. Peter Varhol and Gerie Owen explain that the critical difference between the two flights was the interactions of their respective aircrews. United Flight 232 divided up responsibilities and worked as a team, using Aircrew Resource Management (ARM) to guide how the crew behaved during the flight, and especially in a crisis. Asiana Flight 214 deferred to the captain, neither communicating nor questioning his decisions in crisis. ARM helps cockpit crew members work together to best utilize the whole team’s skills to make flights safe. Using ARM principles, a testing team can bring their project safely home. The leader of a team is the final authority, but leaders must acknowledge team members’ knowledge and experience. This can make the difference between success and failure. Join Peter and Gerie to learn how you can apply aircrew practices to your team’s delivery of high quality applications through complementary expertise, collaboration, and decision-making. You’ll learn how blind deference to authority and automation can be detrimental to a testing team, and how to use everyone’s skills to achieve success.
[video:https://youtu.be/NzYvSmyTcTo width:300 height:200 align:right]
Upcoming Events
Apr 27 |
STAREAST Software Testing Conference in Orlando & Online |
Jun 08 |
AI Con USA An Intelligence-Driven Future |
Sep 21 |
STARWEST Software Testing Conference in Anaheim & Online |
Recommended Web Seminars
On Demand | Building Confidence in Your Automation |
On Demand | Leveraging Open Source Tools for DevSecOps |
On Demand | Five Reasons Why Agile Isn't Working |
On Demand | Building a Stellar Team |
On Demand | Agile Transformation Best Practices |