The 10 "good" reasons NOT to take an ITIL 4 course

1. I've heard a lot about this course...it's boring.
2. I have already installed ITIL version 3 on my PC...and it doesn't work
3. I left my car in the second row...I'll be back in two days
4. I didn't sign up willingly...my boss did.
5. ITIL will not help me quit smoking....
6. I had to study until 1 a.m....
7. Answers to questions are impossible...but you have to get over it
8. Sorry I got the wrong classroom
9. I used to complain all the time that they wouldn't let me take training courses, I won't complain anymore
10. In a few months I will retire....

Whatever your "excuse" is there are also 10 very good "reasons" to take an ITIL 4 course in Service Management ...

1. 1990 - At&T network collapse. A small mechanical problem in one of the phone company's stations causes 75 million phone calls to "drop," which no one answers because of the failure, which then infects several other company centers in a chain, causing them to crash. No hackers, just the fault of a faulty line of code added during a software upgrade process. To get an idea of the consequences just think of American Airlines, which lost something like 200,000 reservations because of this bug.
2. 1983 - World conflict touched. Soviet warning system sends out wrong information and World War 3 comes close. All the fault of a bug in the software of the Soviet warning system, which detects five ballistic missiles coming from the United States. Good thing the officer on duty, Stanislav Petrov, has a suspicion and does further checking: it would have made no sense, he later explains, for the U.S. to attack with only five missiles. And he is right: it did not.
3. 1998 - Mars climate observation and measurement problems. Two spacecraft, the Mars Climate Orbiter and the Mars Polar Lander are part of a program to study climate and weather on the red planet. Due to a navigation problem in Lander flew too low and was destroyed-all the fault of two different measurement systems used on the spacecraft.
4. 1996 - Ariane 5 explosion. The brand new rocket with attached European satellite blows up seconds after launch for its maiden voyage. The self-destruction is caused by internal software that mistakenly tries to put a 64-bit number in the space of a 16-bit one. Cost of the disaster: $8 billion.
5. 1999 - 2000 The millennium bug. When midnight strikes on December 31, 1999, the announced disaster does not actually arrive. But the Millennium Bug ranks high in the amount of money spent to anticipate the damage: more than 500 billion euros.
6. 2006 - Incompatible software on the Airbus A380. When one program doesn't talk to another, it's trouble. As in this case, when there is a miscommunication between two of the consortium organizations producing one of Europe's largest passenger planes. A Hamburg factory uses an older version of CATIA software and the French company Dassault Aviation uses the latest version. So when the two halves of the plane are put together, the software does not match and internal connections are impossible. Even the cables are incompatible, and they all have to be replaced. The "carelessness" costs a lot of money-though no one later wanted to quantify it-and delays the program for a year.
7. 1999 - Siemens and British passports. In the summer of that year, half a million British citizens do not receive their passports on time because of an insufficiently tested Siemens computer system. Hundreds of people cannot go on vacation and the government is forced to pay millions of pounds in compensation.
8. 2004 - EDS and (CSA) the child support agency. Due to the introduction of a new computer system during the restructuring of Britain's CSA (the child support agency) nearly two million people are being overpaid by commercial services giant EDS, while 700 thousand are receiving underpayments. The result: the agency's collapse and a cost to taxpayers in the billions.
9. 2007 - Los Angeles airport in a tailspin. Once again because of software 17,000 flights remain grounded at the Los Angeles air terminal. All because of a network "card" that instead of shutting down keeps inputting wrong data into the system. The system goes haywire and no one can enter or leave the airport for eight hours.
10. 2006 - Exploding laptops. The most egregious case was that of Dell, when a company laptop caught fire in the middle of a trade show, in front of cameras and a large audience. But the problem of laptops catching fire quickly spread. Faulty batteries were blamed, and more than four million were recalled. The case also touched Ipods and Macbooks.

Source: Claudio Restaino & ZdNet Australia