views:

759

answers:

6

I find The Joel Test to be a nice, straightforward tool to diagnose a company. I just ran it on my company and we scored 5/12, its time to improve or we are out of business. I want to bring up The Joel Test on our next meeting with our boss, who has no programming experience.

How do I best convince him that The Joel Test is a good standard to adopt, besides rational arguments like productivity loss? Rather, I look for referencing famous persons, books etc that praise it, buzz words or other ad hominem arguments that might convince my boss.

+1  A: 

Potentially your boss won't care but you can also mention that Joel tried this and succeeded so he's not making this thing up. Also almost every known successful software doing these one way or another so pick 5 of them and show them as examples.

Beside of that I think focusing the money and obvious short - long term effects will get their attention.

dr. evil
+5  A: 

our boss, who has no programming experience

My humble guess is that non programmers won't understand the Joel test. I guess the test is more useful for team leaders that are also programmers.

Here's a tip: try having some person (maybe you?) responsible for some small scale software project and have that person apply the Joel Test on that project. Then show how it improved (or not...) the overall code quality, delivery time, etc. Proven results are much more convincing than referencing famous persons.

João da Silva
+12  A: 

I wouldn't waste your time.

Bosses get bombarded frequently by people professing to be experts (MBAs and such) in various fields and attempting to impose their metrics on poor unsuspecting targets.

Don't get me wrong, I enjoy Joel's stuff, but has the Joel test ever been seriously tested? Until it's been through some rigid correlation with blindingly successful (scoring high) and dismally failing (scoring low) test cases, it's just one guy's thoughts.

So why should anyone take any notice of it?

paxdiablo
Nothing against Joel, but you're right
Robert Gould
fwiw, I think the scoring system on the list isn't especially realistic anyway - it's better as an interview measure
annakata
+1 from the owner of a small software house. It has some nice ideas but huge gaps, notably that it ignores users and requirements.
Shane MacLaughlin
Joel Test is a bit vague as well "Best tools money can buy"... who's opinion of "best" are we asking? How about diminishing returns? Do I need a machine with three 30" monitors and 15000 dollars worth of hardware inside?
TM
+6  A: 

Don't.

Convincing someone who probably never heard of the guy that we should all follow The Teachings of the Great Joel Spolsky seems like a very inefficient way of convincing your boss that in order to do your job well you should have things like build servers, quiet offices and good tools.

If you want a build server then convince your boss of the benefits of having a build server. If you want a quiet office then tell your boss that you work better that way. If you can't convince your boss that way then you won't impress him referring to a list of points from someone he never heard of.


@Pax: You have two options to convince a manager to implement Joels list. You can sell the list or you can sell Joel. I was just trying to reflect how the second option will sound to a manager. :-)

Mendelt
"the Great Joel Spolsky" seems so ... harsh. I tried to phrase my answer to not insult him, since he has a *lot* of good ideas in my opinion. But bosses won't listen to him since he's not an MBA, just an incredibly successful businessman who practices what he preaches :-).
paxdiablo
@Pax: Correction: Joel *preaches* what he *has practiced*...
Brent.Longborough
+13  A: 

Don't waste time changing people's minds.

Instead, do the following.

  1. Apply the Joel test.

  2. Find things in your organization that are broken, and the breakage is identified by the Joel test. Not everything that's broken is identified by the Joel test. Not every failure in the Joel test is actually something broken. People cope and compensate really well.

  3. Rank the broken things in order of fixability.

  4. Fix one thing.

  5. Document the connection between the Joel test and the fix.

  6. Repeat the process on the new organization.

Don't waste time educating your boss. Fix things. Your boss is on their own to lead, follow or get out of your way.

S.Lott
+1  A: 

"or other ad hominem arguments that might convince my boss"

No ad hominem argument should convince anyone ever, that's rather the point.

annakata
Ad hominem *attacks* should never be tolerated but ad hominem *arguments* can be useful if the "hominem" in question (I can't remember all those Latin declensions and tenses I learnt many moons ago) is a credible source.
paxdiablo
(forgive the dupe from above) - Useful because people believe them, but any ad hom statement is still a fallacy, and no matter how good the source is the source can later be discredited so it's not even safe. What you want to do is understand and use the Donald Knuth characters argument.
annakata
@Pax: It's "homen" in question. LOL
Brent.Longborough