I think the problem I had with this statement is the "anyone can refactor anyone else's code" part. Although it's basically true, there needs to be a team culture that steers when it's ok to just refactor the code, and when you need to consult the original author. It's something a team that isn't used to this way of working actively needs to learn.
One of the challenges that agile teams need to overcome is ensuring that developers are responsible. At
When Does(n't) Agile Modeling Make Sense? I state: You require responsible and motivated developers. Agile software development requires developers that have the discipline to work together to develop quality software, and who are often generalizing specialists. The implication is that you need a healthy team environment, one in which people trust one another and help each other to succeed. Contrary to what many of the detractors of agile development will tell you, my experience is that you don�t need people that can walk on
water instead you simply need people who want to get the job done and who have the ability to work with others effectively.
- Scott
<a href="http://www-306.ibm.com/software/rational/bios/ambler.html" target="_blank" rel="nofollow">Scott W. Ambler</a><br />Practice Leader Agile Development, IBM Rational<br /> <br />Now available: <a href="http://www.ambysoft.com/books/refactoringDatabases.html" target="_blank" rel="nofollow">Refactoring Databases: Evolutionary Database Design</a>