This looked so interesting I had to post it:
"Myths in Software Engineering" -
A few of my favorite myths:
- Software development consists of discrete, separate activities that can be organized into phases
- The best way to make the *overall* process effective is to have efficient specialists for each phase
- These specialists should produce artifacts that are "intermediate work products", to be handed off to the next person in the chain
... and my personal favorite:
- If you didn't write it down, it didn't happen.
If you enjoy this kind of thing, there is a great little book called "Facts and Fallacies of Software Engineering" that goes into much more detail. If I recall correctly, fallacy #1 is "Without metrics, you can't manage."
What are some of your favorite myths in software engineering?
Schedule and Events
March 26-29, 2012, Software Test Professionals Conference, New Orleans
July, 14-15, 2012 - Test Coach Camp, San Jose, California
July, 16-18, 2012 - Conference for the Association for Software Testing (CAST 2012), San Jose, California
August 2012+ - At Liberty; available. Contact me by email: Matt.Heusser@gmail.com