G(r)ood Testing 12: knowledge of plane crashes can help to prevent IT disasters

In my new column is a follow-up on the G(r)ood Testing 11- Explosive software – when risks do count. In this 12th edition of G(r)ood testing I talk about the lessons that we can learn from space and air disasters: Unlike in the average software projects, when a plane crashes, extensive research is done to understand the causes. So these research reports are  an instructive read for tester that want to understand why problems occur. It also challenges us, do we do a good job?

We know that most disasters occur through an accumulation of several small and seemingly innocent errors. Should we not combine the errors we found in order to investigate scenario’s that might have an unexpected impact? I requires a shift in mindset and some people might see it as seeking problems instead of killing them. But it will be rewarding for those that want to add value and prevent IT disasters from happening.

Read the full column on the EuroSTAR community pages. Enjoy the read.

This entry was posted in EuroSTAR, G(r)ood testing, Video and tagged , , , , , , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s