
Establish a schedule for transition team meetings, for transition reviews, and for
reports to the development project team, the production support manager, and
any other C&C units involved in the transition of this application. Determine how
reports are to be made (at project status meetings, at project review meetings,
through email, etc.). Use the project stakeholder table to determine who has a
stake in the transition progress.
The following methods will be used to keep stakeholders and outside parties
informed and involved in the transition process:
Stakeholder Method of
Communication
Frequency of
Communication
Transition Team Face-to-face informal
meetings
Transition Team
Meetings
Daily
Monthly before ramp-up,
but weekly during
transition
Project Team Project Status Meetings Weekly
Project Sponsor Project Status Report Monthly
C&C Director Project Status Report Monthly
Project Steering
Committee
Project Status Report
Project Status Meeting
Monthly
On demand, when issues
require it
Project Manager
Team
Committee Meetings
Global Issues Log
Semi-monthly
On demand
End Users and
other
stakeholders
Project Status Report
Transition Status
Notification by email
Monthly
When application reaches
steady-state production
Outside Groups,
such as vendors
Business letters As needed
This table shows the categories of stakeholders. You should add the actual
names for your project's stakeholders in each category. The communication
methods and frequencies included in this table are recommended, but you may
add additional communication techniques, or modify these if necessary.
Timelines and Milestones