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."
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.
I couldn't follow this at all. Can you put it in a PowerPoint for me? Thanks.
"We shall redouble our efforts"
The commander of Death Star 2 when Vader told him the Emperor was coming to inspect the project.
where wrestling is considered Science Fiction. I continue to wait for them to start rolling COPS episodes and Bizarre Foods.
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
I think I should go back to ancient and venerable Slashdot practice and avoid reading TFA. In fact, I'm not so sure about the summaries, either.
And the comments...
well,
Good bye, it's been fun.
Do not mock my vision of impractical footwear
Outsource when you can't do a job yourself?
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.
No movies will teach you about real skills needed for efficient project management. People who possess those skills are usually busy doing something else and consider their PM as pure overhead. It doesn't mean you have to be harsh with them. I mean help them as much as you can, sometimes, they might even cover your ass and take the hit for you if they are good PM.
Everything I write is lies, read between the lines.
Even if I dial my nerd pedantry down to the level where I twitch only slightly when somebody calls Star Wars 'sci-fi' on account of it happening in the sciency environment of space, I can't allow 'Buffy the Vampire Slayer' to be called SF without comment. I just can't. The lesson Ms Pinchefsky dragooned Buffy into was "Motivate your team members". Setting aside the question of whether any skull thick enough to not have already picked up advice that general is going to have the Eureka moment from reading a forced analogy to a TV show: is Buffy the only work of fiction from which we could squeeze this lesson? Of course not. In Dune, did the future Kwisatz Haderach not motivate the Fremen? In Battlestar Galactica, did Commander Adama not motivate his team at some point? I assume he did. I'm no Pinchefsky, admittedly, but still I can't shake the thought that she could have found some muse that did not muddy an already much-abused designation.
And actually it seems my outrage this evening had not met its limit at the outset of this post, which I thought it surely had, but having read about the episode from which Ms Pinchefsky seized her lesson, it turns out to be *even worse* than an improper use of the term SF. Buffy is fired for screaming at patrons that they are eating human meat. Should we really be taking management lessons from the woman who hired her back? Don't do that! Don't rehire employees who are literally screaming bloody murder at the customers! They are bad employees, and you are better off without them. This insightful management lesson from fantasy I offer to you for free.
My main point is that seeing this bullshit offered without even some mild qualm just makes me depressed about Slashdot.
I bet there are a lot of lessons there, including not giving your agents too much independence, they could screw things so badly that you will need to hire your enemies to get rid of them.
After the scene has been set and you embark upon your heroic and seemingly impossible mission, spend 90% of the project avoiding peril after peril, until just before the end you cause the whole thing to blow up.
And definitely don't hold out for the sequel where pretty much the same thing happens again.
Here are the real lessons of Sci-Fi movies.
Wherein the Evil Empire sets out to destroy the Androids that could result in its' destruction, but fails due to some major design flaws (and some seriously bad public relations issues), and is ultimately destroyed by its' own hubris.
Team! You either make the deadline, or you die a horrible death in the hands of our local corporate lawyer. Your choice.
Then you have bigger problems than lacking business skills.
"Never tell me the odds" and then plow through it like crazed cowboys
Table-ized A.I.
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."
For God's sake put an off switch on the damn machine.
Or, always plan an exit strategy before you implement a can't loose solution.
Don't plan ahead, try to foresee difficulties and solve issue way before they come up. Instead blow things off, leave out important details and try to solve everything at the last possible moment. That's good management, or at least a interesting movie
sarcasm off
Did you know 80 to 90% of the moderators on slashdot wouldn't recognize a troll even if one dragged them under a bridge.
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?
Applebuck Season: You're less productive working 80-hour weeks than you think you are. The whole "lean in" thing is killing you, AJ. Stop and ask for help.
Suited for Success: Stop worrying about what the customer wants, deliver what the customer actually needs.
Owl's Well That Ends Well: The n00b isn't necessarily there to take your job, they might have just been hired to ease your workload. Stop being a dick to the new guy/gal.
Lesson Zero: Stop worrying about the deadlines. If it was important, the ship date would have slipped.
Hearth's Warming Eve: The devs (earth ponies) blame arrogant QA/process weenies (pegasi), the QA department blames management (unicorns) for impossible demands, management blames those slacker devs, and society collapses under the ineptness of its own org chart.
Wonderbolts Academy: At first glance, it's a "Top Gun" parody, but upon reflection, this is basically how XP/pair programming worked.
Apple Family Reunion: Is this episode about Thanksgiving, or is it about HR departments and teambuilding exercises?
Just for Sidekicks: Managers, this is what your underlings are actually up to while the brass is in town. (Games Ponies Play: Grunts, this is how inept your managers are at trying to impress the brass while they're in town and you're slacking off.)
Princess Twilight Sparkle: The first ten minutes is about matrix management and cross-training. The second ten minutes is about the fact that it doesn't matter as long as you sell the company and everyone gets a fat check at the exit.
I like to find leadership lessons from unusual places too. I occasionally write about them on my blog. This year, that included IT leadership lessons from Zombies, and leadership lessons from My Little Pony: Friendship is Magic! Coaching Buttons blog :-)
in agile
There is not a shred of SF in Gravity. It is a modern disaster movie.
Can't comment yet, still filling out form Reply-13-12.19.
If you haven't seen it, there may be spoilers.
THX 1138 surprisingly by George Lucas.
http://www.imdb.com/title/tt0066434
The ending is a lesson for project managers.
"Any sufficiently advanced technology is indistinguishable from magic."
The best lesson to be learnt from Aliens is one that doesn't just apply to project management, it can be applied to meetings, presentations etc in all walks of life:
"Any questions?" .......
"How do I get out of this Chicken Shit outfit?"
Do not let a private company take over what should be government's job.
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
If the client requests a change mid-sprint, test their part in the decision via Amtal Rule.
May thy knife chip and shatter!
The answer is, of course, fuck all.
What the author meant was:
Here's what I think about project management skills, and here are a few vaguely coincidentally similar situations in sci-fi movies to make me look nerdcool
systemd is Roko's Basilisk.
It is Bean the one who first sees the potential in those misfits and castaways and assembles the team for Ender to command.
I avoided Ender's Shadow for a few years thinking it would be just a rehash of a great book (if you haven't read it don't watch the mediocre movie before reading the book), but it is actually pretty good.
Violence is the last refuge of the incompetent. Polar Scope Align for iOS
Because that would mean workers putting in a 72-hour day.
Why make one when you can have two at twice the price!
The Robocop example is really the 'first waffle' concept. You always have to make a first waffle, and it's almost always bad -- the iron's just not warm enough, oily enough or whatever until the second one comes out. But there's always, by definition, a first one. So just plan on your first iteration of a project to fail and to start over and do it right based on what you learned about the wrong way to start. Or not. Either way, the first iteration fails. You can throw it out and start over, or you can try to make the best of that ruined waffle. So why not plan on it?
Also, read "The Mythical Man Month". Amazingly, there are managers (and managees) who haven't. They don't have time? Really, you don't have time not to.
And how did the author of TFA miss the best one: pad your time estimates like Scotty.
I am not a crackpot.
Star Trek: Make It So: Leadership Lessons from Star Trek: The Next Generation It's a good discussion of management techniques.
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.
You know what Sci-Fi can teach you about $REALLIFE? Nothing. Because it's fiction. You can learn things from real life due to this little thing called causality. In books, effect follows cause not necessarily because it really would in real life, but because the author chose it to happen.
Some brokerage house ran an ad years ago something like "What can a picket fence gate teach you about investing?" Of course the answer is the same. Absolutely nothing. However, you can learn about investing AND learn about picket fences and discover commonalities. In no way have you used what you learned about fences to understand investing.
Ask Scotty to beam them up.
Thats true management there.
What can happen when the boss has an ulterior motive of which the staff is unaware. Worse yet, that motive requires that the project, as officially defined, must fail miserably.
I've been on a number of in-house projects where someone up the chain got a call from some outside vendor. If only your project were to fail, we could be brought in to consult/rescue it/sell your company our technology. And you'd get a kickback for that.
Pay no attention to the entrails of your staff splattered about the landscape.
Have gnu, will travel.
The pitfalls of treating staff as interchangeable resources.
Have gnu, will travel.
Clearly there was a major flaw in the requirements stage for this - the person who omitted "The project must not enslave humanity." has a lot to answer for, although it's possibly it was just due to vague requirements specification and there was a "The project should not enslave humanity." in there, that the developers felt they had to work around in order to achieve the management goals.
Other than that though, it's a wonderful example of project management on a very large systems engineering effort gone right. The system's so robust that it *kills* people who try to introduce bugs or take it down, it integrates with a completely incompatible outside system seamlessly (pre-dating Plug And Play by decades), the resulting combined system scales well (it's too old to be web scale, so shut up), it's not beyond using the threat of nuclear destruction to make sure its deadlines are met (and hopefully to target people who ask if it's web scale) and it not only patches itself, but by the end of the movie it's fully in charge of its own SDLC and is working on writing the next major release without outside intervention. Other than the killing people and enslaving humanity bit, which can be characterized as a feature as well as a bug, who *wouldn't* want to manage a project like that?
I find pornographic films to be more analogous to business. Because no matter the industry, somebody is always trying to f*c you.
"I'm here to put you back on schedule."
Have gnu, will travel.
Wrong hero: not the Greatest American Hero.