What happens when you don’t make requirements crystal clear? They’re wide open to misinterpretation. Enjoy this video clip and remember…it doesn’t really matter what method you use to capture project requirements; if they’re too fuzzy, you’re gonna pay for it one way or another!
Family Guy - Peter gets Chris a new pet,
but misinterprets transportation requirements.
(Video clip courtesy of Hulu)
Related articles by Zemanta
- Customer, Developer, Tester (codebetter.com)
- Functional specs (slideshare.net)
- Software requirement (slideshare.net)
- How do we solve business problems from a customer-centric approach ? (slideshare.net)
- eXtreme Project Management. Both Brilliant and Dangerous. (edge.papercutpm.com)
- Garbage In, Garbage Out. Haven’t We Learned That Yet? (edge.papercutpm.com)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=3f57ba50-f52f-48e5-a1e6-c64fd42a4e2c)
Like this article? Why not spread it around?
I'm Geoff Crane. After 22 years in the trenches of a lot of tough projects, I decided to change direction a little bit and focus on sparking ideas in the vibrant field of project management.
If you're a project manager, or even if you're one voice in the project choir, you are in a position to be truly remarkable. Without exaggerating, you have within you the capacity to change the world, just because of who and where you are!
How do you access that part of yourself? Please get my free project leadership advice and free ebook "Nine Destructive Behaviours" and join my rapidly growing community!
Pingback: Tweets that mention The Importance of Precision » Papercut Edge -- Topsy.com
Pingback: Annual Cost of Project Failure «Papercut Edge
Pingback: Lights, Camera, Disaster! The Corporate Video Quandary «Papercut Edge