Slashdot Mirror
What Sci-Fi Movies Teach Us About Project Management Skills
Esther Schindler writes "It's certainly fun to pretend to find work inspiration from our favorite SF films. That's what Carol Pinchefsky does in two posts, one about positive business lessons you can take away from SF films (such as 'agile thinking can save many a project (and project manager) in a crisis' from Robocop and team motivation lessons from Buffy), and the other, 5 Project Management Horror Stories Found in Sci-Fi Movies, with examples of the impact of poor documentation on Captain America."
"We shall redouble our efforts"
The commander of Death Star 2 when Vader told him the Emperor was coming to inspect the project.
I mean you have Star Wars, Star Trek, Senerity, Farscape (I guess), Dune (maybe). A few movies from the 60's/70's (silent running, 2001, whatever).
What other sci-fi movies are there? It's all shit.
Alien. Aliens.
... when there's science involved (look at me still talking ...)
It's a stunning reminder of the value of human life
- Nec Impar Pluribus, or so I'm told.
What other sci-fi movies are there? It's all shit.
According to TFS, Buffy is Sci-Fi. I knew right then not to read the article.
My God, it's Full of Source!
OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
Don't let Khan near anything.
If it breeds, it can take over your ship.
Sleeping with the test proctor will let you beat the no-win scenario.
If you have a bad feeling about something, it's a trap.
Should have a prominent big red self destruct button. This button should not do anything, and it should be booby trapped.
I'm trying to teach myself to set people on fire with my mind... Is it hot in here?
I do always hate it when science fiction and fantasy get mixed in together as "genre films." I have nothing against fantasy, mind you. And I'm aware there is a lot of crossover, especially among genre writers. But the two are very different forms in many ways. Sure, you can intermix them--in the same way you could make a science fiction noir detective story, or a science fiction sports movie. But fantasy generally incorporates implausible or supernatural elements, whereas science fiction stories generally stick to elements that must at least be justified as POSSIBLE in their setting. Not that the lines don't get blurred sometimes.
The cow says "Moo." The dog says "Woof." The Timothy says "Thanks, valued customer. We appreciate your input."
How can you write about IT project management failures in sci-fi movies and not mention Jurassic Park?
For all Malcolm's talk about "chaos theory", the failure of the park was a very predictable result of (1) relying heavily on IT for mission-critical systems, and (2) putting all of this IT infrastructure in the hands of one guy, that the CEO knows is disgruntled! Any project manager with half a brain should have seen it coming. But Hammond, who "spared no expense" on everything else, apparently couldn't be bothered to hire a competent CIO, or spring for a real IT team.
A general rule of project management, not only in IT but in other fields as well, is that you should never have critical, undocumented knowledge that is in the possession of only one employee. The reason is obvious: if that employee quits, or is fired, or gets hit by a bus, or is eaten by a Dilophosaurus, you're completely screwed. All mission-critical systems should be covered by multiple people and should be properly documented.