The Joel Test - 20 Years On

The Joel Test was created in August 2000 by Joel Spolsky, a software developer from New York City, who is a founder and CEO of Stack Overflow, creator of Trello project management software, and ex-Microsoft employee.

The test is designed to rate the quality of a software team, all in about 3 minutes! It consists of 12 ‘Yes / No’ questions that are intended to be quick and simple to answer.

A team is given 1 point for each ‘Yes’ answer - the higher the score the better. So a score of 12 is perfect and means that you have an effective, disciplined team that can deliver. Of course the test evaluates the software team and not the software, so you can have a perfect score and still produce an unsuccessful end product.

The Joel Test

1. Do you use source control?

2. Can you make a build in one step?

3. Do you make daily builds?

4. Do you have a bug database?

5. Do you fix bugs before writing new code?

6. Do you have an up-to-date schedule?

7. Do you have a spec?

8. Do programmers have quiet working conditions?

9. Do you use the best tools money can buy?

10. Do you have testers?

11. Do new candidates write code during their interview?

12. Do you do hallway usability testing?

Does each of the questions in the test carry equal weight? 

Do you care about some points much more than others? Question 8, ‘Do programmers have quiet working conditions?’ was one of the most discussed points in 2000 and is a question that generates much debate today. Spolsky grants every programmer their own office, with natural light, at each of his three companies. This goes against the trend of open plan co-working spaces where some programmers feel the need to wear headphones to block out distractions. Too, in 2020 with a considerably higher % of programmers remote working, one person’s home working reality (quiet, physical space, natural light) won’t necessarily be the same as another’s!  

20 years on how valuable is the Joel test? 

Among RWA’s clients the Joel test is still used and a score is included in company details or job descriptions. They probably won’t score a perfect 12 (Microsoft consistently scored 12/12 and in the original Joel on Software blog most software companies were said to run at 2 or 3), but a score of 9 or 10 will give new hires confidence that they are joining a company that strives to build effective software teams.

Contact us to find out more or browse our latest jobs.