Continuous Integration is a method that gets you around integration hell.
Health of the repository's mainline is everything.
The integration server is the reference for everyone.
Highest priority: Fix broken integration.
Don't commit broken code and don't checkout broken code into your workspace.
Automated Test Coverage would be great
Execution of Acceptance Tests would be the full monty.
Preserving consistency of the installed IDEs.
In addition to a short talk, you have to prepare the infrastructure for the lab and maintain it at least at the beginning of the lab.
During the lab you will have to take care that somebody takes care about the consistency of the installation and the CruiseControl integration. (Which usually means that you have to do it on your own at the beginning and to train others as soon as possible.)