It's easier to install Coda when you have a little experience in doing so, but that's true of a lot of software. Begin by doing a one-server cell with one additional client. This will give you the feel of the software and remind you of some critical issues. Next try a small, real cell with two or three other users. To learn the backup system, get it working, then do a full backup and two incrementals on successive days, then delete the whole cell and restore it. This will be very painful.
You will probably need to edit many of the scripts that come with Coda; I had to change seven of them for my use, but then I don't like to install every executable in /usr/bin.
If you use Coda, you ought to join the Coda mailing list, or at least find an expert to help you over the rough spots. The mailing list is very friendly and (within reasonable bounds) very tolerant of newcomers.
If I say `beware of prepackaged binaries', I don't mean that you shouldn't use them, but that they may make choices which you ought to change. I suspect most people will find a prepackaged binary is the best way to try Coda for the first time, but I don't think any of them should be used in a production cell.
It is worth reading through the main documentation carefully. Also look at recent archives of the mailing list; the problems you face have probably bothered someone else, and the solutions probably exist already.