Identifying problem personal

Today we had a very useful lecture - under the subject Rapid Application Development in my MSc. Thought of sharing some with you... this is related to identifying problem personal in your project team. Make sure you do it right at the beginning - otherwise you loose...
-They try to Cover up ignorance rather than trying to learn form teammates
-Have excessive desire for privacy(“ do not need anyone to review my code”)
-They are too territorial (“No one else can fix the bugs in my code. I will attend to them next week”)
-Grumble on team decisions and continue to revisit old discussions after the team has moved on.(“I think still we ought to go back to our last decision and change it to the other option”)
-Other team members will make complaints about the same person
-Do not pitch on team activities. (Asks for holiday 2 before a major product release)