Common understanding

Depending on the project environment, you may need to do other things as well to encourage collaboration. For example, when the project is not too small, it would work better to make it clear what is expected from each person, and what they can expect from others. What I just mentioned is one of the principles in PRINCE2^® (a project management methodology). Going further, you may even need to formalize the flow of works in the project; e.g., each design document has to go to ##### for peer review; the peer reviewer should respond in less than ##### days; then it goes to…

Besides responsibilities and flow of work, you may need to make the basic behaviors clear too, with some ground rules that everyone will respect when working together.

You may be thinking it may be bossy to tell people all of these things, and as such, a violation of the previous principle. That would be true if you set all of those things. The best way, however, is to facilitate the team to set those rules themselves whenever possible. That way, the rules will be more realistic and the acceptance of the team members higher. For example, the P3.express Code of Conduct that was mentioned above was developed and adjusted by the community of practitioners rather than being dictated from the top downwards.