I ran across a quote in Christopher Duncan's, "The Career Programmer: Guerilla Tactics for an Imperfect World" that made me both laugh and sigh.
You need to consider one additional thing when trying to convince management the current approach to developing software needs improvement. What do you do if non of this sways them and they insist on continuing with chaotic development approaches that consistently create disasters and stress? Update your resume. Life's too short to work for clowns.
So the question becomes, do you work for clowns? Does the development process at your company make a circus look like a well-oiled machine? You might work for a clown.
I plan on putting together a complement to The Joel Test where instead of a list of things a company does before you consider working for them, The Clown Test would be a list of things that indicate you might work for clowns.
This might describe your boss,
- if he thinks an estimate is a promise,
- if he thinks developers are interchangeable with no effect on the schedule,
- if he thinks its ok for the lead developer to publicly berate a junior developer,
- if he thinks requirements documents are a waste of time,
- if he thinks the only place for designers is at a fashion show,
- if he thinks he just needs one good programmer who can code anything,
- if he thinks that people whine too much about teamwork,
- if he believes in Silver Bullets,
he might be a Tech Clown.
My apologies to Jeff Foxworthy.
When you run across a good example of a Tech Clown, send 'em my way and I'll add it to the list for every one's enjoyment.