No subject

    1. Merge soon, merge often.
    2. Split source code maintenance.  That is, a source file, module or
       whatever is assigned to one and only one developer.  So large
       merges become trivial.

Wiki browsing may also provide you some insight about it:

    http://www.selenic.com/mercurial/wiki/index.cgi/CvsInfo

Nevertheless, if the rest of the team do not put some interest on
understanding the tool, it is very difficult to use a DVCS system.

Cheers.

-- 
Isaac Jurado
http://www.krenel.net

"The noblest pleasure is the joy of understanding"
Leonardo da Vinci