TOP TOC 
Agile . since Jun 23 . Index . DOCs TOP TOC
States Beck: "A real customer must sit with the team, available to answer questions, resolve disputes, and set small-scale priorities. By 'real customer,' I mean someone who will really use the system when it is in production" [1].
There is an old joke about involvement versus commitment: if you're fixing bacon and eggs for breakfast, the chicken is involved, but the pig is committed. This is absolutely true of the customer/user on an agile development project. People who are going to be using the system are responsible for defining how that system is going to work, and their commitment is for the period of the entire project.
The total commitment of the user is one of the major hallmarks of an agile development project. Users are as responsible for the definition, user interface, review, test case presentation, and prototyping of the end product as anyone on the team. Because of this, there is very little finger-pointing when the product is delivered for broad installation and use.
Agile . since Jun 23 . Index . DOCs TOP TOC
Finally, there is the issue of coding standards. Because ideas of pair programming, collective ownership, and (let me not forget to mention) minimal documentation, it is critical that all of the code follow very strict guidelines. In this environment, "you simply can't afford to have different coding practices. With a little practice, it should be impossible to say who on the team wrote that code" [1].