The importance of a structured team in programming

It is 3:12am, Sunday Morning. The reason I'm not sleeping right now would not have occurred had the following been considered.

I'm finding out with my recent exposure to an absolutely unstructured dev team: Subversion is not enough to structure a development team.

Here's some things to look out for:

Testing:

• How is QA handled?
• Do programmers have any automated testing (unit testing, regression testing, etc. -- separate post on this coming soon)?
• How are server and general configuration issues handled?

Development:

• How do programmers know what other programmers are working on?
• Are the latest versions of requirements and resources (Copy Decks, Mocks, etc.) being used?
• Is there anyone responsible to handle branching and tagging, or is that done ad hoc?
• If programmers are located remotely, how are their contributions kept visible to the local team?