Why does it assume that Collective Code Ownership = Anarchy? It simply means that anybody CAN edit the code, not that everybody WILL DO everything. After all i

Why does it assume that Collective Code Ownership = Anarchy? It simply means that anybody CAN edit the code, not that everybody WILL DO everything. After all it's a matter of common sense: If I don't understand what's going on, I will not touch it (this address the slow delivery drawback). All the other points against Collective Code Ownership seem a little empty as well: inconsistencies are not result of collective code ownership, but poor organization. Agile Programming != Anarchy