3 Triumphs, 3 BreakdownsBy Kim S. Nash | Posted 2003-01-01 Email Print
WEBINAR: On-demand webcast
Next-Generation Applications Require the Power and Performance of Next-Generation Workstations REGISTER >
What did it take to get noticed last year, for better or worse? Big numbers.
Do project managers learn from their mistakes? As a profession, the record suggests no. What dooms a technology project can be parroted by any sleepy MBA student: workers who shun change, corporate politics, poor management.
"We, in this profession, can't seem to learn from failures," says Mark Keil, associate professor of information systems at Georgia State University. While aviators, civil engineers and others systematically study failures to avoid future mistakes, technology managers largely don't, says Keil, who studies failed tech projects. "There's a tendency to sweep them under the rug."
Buggy software can damage a project. Yet, decisions made by project leaders during an implementation can impact the outcome. Perhaps proving that point: Oracle software was involved in both a Baseline triumph and a breakdown from last year.
It's just as critical to look at what goes right. The lessons are there. Here are three triumphs and three breakdowns from the past year.