120 likes | 275 Vues
The Titanic project serves as a cautionary tale in IT project management, showcasing the impact of compromised safety features and aesthetic decisions on project outcomes. Despite White Star's belief in it as the safest ship, poor risk assessments led to a disastrous fate. This analysis explores how the pitfalls of the Titanic mirror common pitfalls in IT projects, highlighting the importance of managing risks, making informed decisions, and learning from past failures. Apply these lessons to ensure your IT projects sail smoothly, avoiding the iceberg of mismanagement.
E N D
“Titanic Lessons for IT Projects” IT Projects from Hell
White Star invested in ship-builder’s model (IT pilot).Used to analyze all exposures to the possibility of loss.
Titanic’s construction stage integrated many complextechnologies and selected safety features to reduce risks
By end of construction Titanic’s safety compromisedseverely. But White Star believed it safest ship ever built.
Decisions with esthetic factors compromised individualsafety features and escalated the level of risk
Two assessment groups surveyed for damage. Bruce Ismaymade fateful decision to prove Titanic could save herself.
Lessons learned - what can you take from all this. YourIT project is little different to Titanic’s project.
Joke • Apparently the computer giant IBM decided to have some parts manufactured in Japan as a trial project. In the specifications, they set out that they will accept three defective parts per 10,000. When the delivery came in there was an accompanying letter. "We, Japanese people, had a hard time understanding North American business practices. But the three defective parts per 10,000 have been separately manufactured and have been included in the consignment. Hope this pleases you."
http://www.pmiwlec.org/Presentation/ITLessonsTitanic.pdf http://www.ccnr.org/fatal_dose.html Ongoing Saga of the Project From Hell http://www.4pm.com/articles/hell.html http://www.wsdot.wa.gov/tnbhistory/Connections/connections2.htm