[kensai]

If you really want to improve the Joel Test, fine. The suggestions are even right. But please, KISS. The original test had 12 items, this one 20. This should be the upper limit, more or less, for any improved version. Otherwise it is probably too long or detailed to be of practical use.

[solatic]

It's also way too specific and biased. Rules like "do you have end-to-end integration tests?" aren't always obligations for all teams, whether that's because your team is doing embedded work or because you're doing something better (like consumer-driven contracts). Other rules like "do you have a primary communication channel?" are even at times counter-productive (in particular, when dealing with a variety of customers who have their own preferred methods of communication, which you must accommodate). Daily status meetings are sometimes unnecessary, if you have a small enough team sitting in its own room or more tightly involve team members in planning and review practices, and indeed daily status meetings often clash with more important practices like flexible scheduling and not interrupting flow.

[ferroman]

Thanks for feedback. We decide that more detailed test - more precise measure, but we still try to keep the list as short as possible.