There are many examples of failed projects all over the world. Like the St. Helena airport, built on a island in the vast open Atlantic Ocean, known for it’s volcanic mountain rising 2600 feet above the sea. The reason for the airport’s opening being postponed indefinitely: “too windy for planes to land” (Source: International Project Leadership Academy). They failed to address the risks or to listen to the advice of experts.

Another project disaster and one of the most expensive scandals in modern history in September 2015, the admission that Volkswagen cheated government emission testing. The engineers intentionally designed and installed a so called “defeat device” into the engine’s control computer. The defeat device was programmed to detect when the car was undergoing emissions testing in order to adhere to the testing limits for clean-air standards. The technology needed to comply with the government regulations was available, but was decided against due to high costs and to protect profit margins.

On a smaller scale project disasters happen quite often, even on IT projects, for example when a record number of high defects are logged during a testing phase leading to re-design and expensive re-development work to the point where committed deadlines are missed or almost missed.

In following good Project Risk Management practice, you will always plan risk management upfront, identify all the risks, perform proper risk analysis (qualitative, quantitative), plan risk responses including assigning risks to owners and then control the risks rigorously throughout the project.

Below you will find a good approach for handling crisis on projects in the Infographic brought to you by Wrike free task management tools.

Let us know in the comments what project management crisis you have come across and how it was handled.