The Joel Test: 12 Quick Checks to Evaluate Your Software Team’s Health

The Joel Test is a concise, 12‑question checklist designed to quickly assess the health of a software development team. Each question can be answered with a simple “yes” or “no,” allowing teams to identify strengths and weaknesses without complex metrics.

Do you use source control?

Can you make a build in one step?

Do you make daily builds?

Do you have a bug database?

Do you fix bugs before writing new code?

Do you have an up‑to‑date schedule?

Do you have a spec?

Do programmers have quiet working conditions?

Do you use the best tools money can buy?

Do you have testers?

Do new candidates write code during their interview?

Do you do hallway usability testing?

A perfect score is 12; 11 is still acceptable, while 10 or lower indicates serious problems. Most software companies operate at 2–3 points, highlighting the need for better practices.

Do you use source control?

Using a source‑control system (commercial packages or free tools like CVS) prevents code loss and makes it easy to track changes across developers.

Can you build in one step?

A good team has a script that can compile the entire codebase from scratch in a single command, producing the final executable and installer without manual intervention.

Do you build daily?

Daily builds catch integration problems early; if a build breaks, the team can fix it immediately, avoiding long‑lasting disruptions.

Do you have a bug database?

Tracking bugs in a database—recording steps to reproduce, expected behavior, observed behavior, purpose, and fix status—prevents forgotten defects and improves overall quality.

Do you fix bugs before writing new code?

Prioritizing bug fixes (the “zero‑defect” approach) reduces the cost and risk of later development, ensuring that new code is built on a stable foundation.

Do you have an up‑to‑date schedule?

An current schedule forces the team to prioritize essential features, cut low‑value work, and keep development aligned with business goals.

Do you have a spec?

Clear specifications guide development and reduce misunderstandings that can lead to rework.

Do programmers have quiet working conditions?

Providing quiet, private spaces helps knowledge workers enter a state of deep focus, dramatically increasing productivity and reducing costly interruptions.

Do you use the best tools money can buy?

Modern, high‑performance hardware and appropriate development tools (e.g., dual monitors, good bitmap editors) reduce friction and keep developers efficient.

Do you have testers?

Dedicated testers catch defects early; a ratio of one tester per two‑three developers is a reasonable baseline.

Do new candidates write code during their interview?

Practical coding tests reveal a candidate’s ability to produce working code, which is more predictive than theoretical questions.

Do you do hallway usability testing?

Brief, informal usability tests with random users uncover the majority of UI problems quickly and cheaply.