Joel Test, something funny and… something less fun

If you make software and you look here, you’ll agree for sure on every point, even if some discussion can arise on a couple of them (read this).
Very serious.

Now read this other document. I’m sure that you’re laughing loud :D.
Very funny.

Now stop a moment and ask yourself the following question: how many points from both the documents you did do/have seen in your experience in the projects you participated? What is the balance between the two points in the two articles? Don’t you feel that what makes you laugh is sometimes more serious than what can seem at the first look because you lived it on your skin? How many times did you feel angry (or simply sad) cause of lack of organization, procedures, tools, conventions and so on?

I’m not saying here that the software production process must be governed like a dictatorship and every smallest aspect regulated, but that there must be a level of organization proportional to the size and target of the project, i.e. big project –> lots of organization and (in some way) vice versa. At a first glance, it may seem that the project will cost much more cause of the organization overhead, but in practice, if organization does not mean only bureaucracy, it will cost less. This is difficult to explain but easy to understand if you look at your project and see it like a complex system, where everything is interconnected and every small change can lead to enormous changes (translated in management language, that means more or less time to accomplish tasks, so more or less money to be shelled out by customers.)

I know that this argument is itself complex and that I’ve only scratched a part of the surface here, but I’m convinced that companies and single developers should dedicate some time (and resources) to at least think about it.

I would like to hear opinions and experience from you.