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.
You don't need to reach for SF to get a great project management lesson, just look at the Apollo program.
A triumph of the human spirit, of technology, of ingenuity, sure - but mainly, an overwhelming triumph of project management. Who says the government can't handle any big jobs, eh? (well, anyone who's been watching for the last 40 years maybe...)
Perfectly Normal Industries
Sounds like it's time for Covey to come back to life and write "The 7 Habits of Highly Effective Fictional Characters."
There's no -1 for "I don't get it."
Sci-Fi teaches us not to hire George Lucas... he's terrible.
Here are the real lessons of Sci-Fi movies.
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.
Not a hip movie to like right now, but Ender's Game is almost all about project management and leadership.
Ender sees the great potential in his team, even in the misfits and castaways, but he also has high expectations for them to reach that potential. That is what I try to do as a leader.
"First they came for the slanderers and i said nothing."
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've been on several projects where I fervently wished "dust off and nuke it from orbit" was a project management option. It is, after all, the only way to be sure.
People who possess those skills are usually busy doing something else
Protip: Linux is successfull because of amazing project management by Linus. Hell, I consider Git a bigger boon to the world than Linux. Anyone can write a damn simple monolithic kernel, but to immediately gather a community and be able to maintain it is a rare skill. Leadership isn't key in sci-fi? Being in the right place at the right time with the right people helps too -- Also evidenced in sci-fi: A rag-tag group of ethnically diverse individuals from all walks of life will save the day! Diversity can help bring new ideas to the table...
Speaking of tables: Don't worry about the time table, if the engineer has to fix it before the deadline, they will find a way, even if it means working overtime: "I'm giving her all she can take captain!" Not to worry, they'll pull some engineering magic out out of thin air during the commercial break because this story arc is about to end.
Speaking of endings: How exactly does Neo see machines as orange colored lights? He didn't get a wireless upgrade, right? Programs escaping into the "real world"? Wait, he can kill sentenals wirelessly with his mind? Yep, instead of a green monochrome inspired world, he's trapped in an amber-screen level of the matrix. The Matrix shows you can always add another layer of indirection...
Look, it's a confirmation bias piece, it's just for fun.
How about Primer?
You're a temporary arrangement of matter sliding towards oblivion in a cold, uncaring universe
Gattaca
When it comes to sci-fi movies, you can't forget that little underappreciated masterpiece
"Science fiction" doesn't have to be pewpewpew Star Wars fantasy. Gravity could be a straight golden-era SF short story.
Science is all about firing a drunk pig out of a cannon just to see what happens.
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.
a few things to make your life more wonderful
1 put your engineers (and security folks) in the best amour you can (hint in space these should be vacuum rated) ,Defense and Fix)
2 always have your basic tools on you (Com
3 Boots are a groovy place to put spare tools
4 CNC should always have medium/heavy weapons "stashed" somewhere
5 You either can Take a Joke or YOU ARE THE JOKE
5 always rig stuff with an extra power input (esp stuff that can go BOOM if it loses power)
oh and the real RoboCop lesson
Your Core Rules should be as short as possible (hint Index card should be all you need)
Any person using FTFY or editing my postings agrees to a US$50.00 charge