A little additional context: Joel's "test" was just a quick-and-dirty way for a job candidate to assess whether or not a company had competent software engineering practices. Assessing your own team's practices could (and should) go far more in depth, since all the messy details are right there. The spirit of this article is good, but I wonder if we can formulate a good test that applies universally to all teams and carries enough detail to help that team improve.
