This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I think that team building / relationships needs to be integrated into each practice, not treated as a completely separate thing, so I think you will find that most of the 20 practices we describe deals with how the team need to collaborate to accomplish various key objectives. As an example, in practice 9 I cover how to describe requirements from a user perspective. Hear I also talk about how you as an analyst needs to e.g. work with developers, testers and tech writers to evolve the implementation (which should include end user documentation) with the requirements. You cannot see those as two separate efforts. So, this practice includes a description of a different set of team dynamics to evolve requirements than most traditional organization have.
However, 2 practices are solely focused on collaboration and culture, Practice 7: Everyone Owns the Product, and Practice 12: Build High-Performance Teams.