MultiSite rollout plan

The rollout actually begins when you begin upgrading the infrastructure at the remote site.

Defining roles and responsibilities

You have to put names to roles during the planning process. Tactically, it will come down to a list of work items:

• Upgrade servers

• Open firewalls

• Synchronize logins

• Create databases

• Install client software

• Provide CM support for developers

Even in the smallest site, you have to designate someone for the last role, what we call the CM lead. This person is the first point of contact when a developer has a question or problem. The CM lead will grow into a subject matter expert.

Training plan

Most of the work of MultiSite is just establishing additional UCM sites that are comfortable enough with the software and processes to take advantage of them.

There are three groups that need training at the remote site: CM administrators, CM leads, and developers. Training will be a combination of formal courses and mentoring from the central site and/or Rational services. Table 12-2 shows a suggested training plan for a remote site that plans to grow to support 50-100 users.

Table 12-2. CM Training for remote sites

Role	Class	Timing
CM Administrator	2-day UCM class	Before ClearCase Administration
	ClearCase Administration	Soon before CM infrastructure setup
	ClearCase MultiSite ClearQuest MultiSite	Mentoring from remote site. Formal training is needed only if the site is targeted to become a peer site: 3-6 months after site has gone live.
	ClearQuest Administration	Mentoring from remote site. Formal training is needed only if site is expected to do any schema customization: 3-6 months after site has gone live.
CM Lead	2-day UCM class	You want each site to have a few power users. Best timing is after a playground is in place. CM lead(s) will grow into subject matter experts and help mentor the development team.
Developers	A one-day version of the UCM class including hands on practice and a walk through of the project-specific usage model. Introduce the concept of mastership in the class.	Right before go-live. Users should be able to go back to their desks and play with the CM environment. CM leads should serve as class proctors.

Readiness review

Final scheduling of the rollout can happen after the remote infrastructure, including connectivity between sites, is in place. Review readiness (Table 12-3) as part of the software project meetings as the rollout day approaches.

Table 12-3. MultiSite readiness review

✓	MultiSite acceptance criteria
	Remote CM infrastructure in place, including local release areas
	Windows and UNIX logins in place
	CM support plan in place
	Replication in place (silent mode)
	Local backups in place
	Lifecycle test complete
	Desktop installations complete
	Developer training complete