csc proprietary communications and training plan for [project] [date] this template provides an...
TRANSCRIPT
![Page 1: CSC proprietary COMMUNICATIONS AND TRAINING PLAN FOR [PROJECT] [date] This template provides an outline structure and suggestions for information to be](https://reader036.vdocuments.mx/reader036/viewer/2022082818/56649e7d5503460f94b7f1dc/html5/thumbnails/1.jpg)
CSC proprietary
COMMUNICATIONS AND TRAINING PLAN
FOR [PROJECT]
[date]
• This template provides an outline structure and suggestions for information to be included in each section.
• To be customized as appropriate for each project/solution• Additional guidance is provided in red text within the slides
![Page 2: CSC proprietary COMMUNICATIONS AND TRAINING PLAN FOR [PROJECT] [date] This template provides an outline structure and suggestions for information to be](https://reader036.vdocuments.mx/reader036/viewer/2022082818/56649e7d5503460f94b7f1dc/html5/thumbnails/2.jpg)
CSC proprietary
Content
1. Introduction (Objectives, Scope, and Assumptions)
2. Audiences
3. Approach
4. Plan
5. Roles and Responsibilities
![Page 3: CSC proprietary COMMUNICATIONS AND TRAINING PLAN FOR [PROJECT] [date] This template provides an outline structure and suggestions for information to be](https://reader036.vdocuments.mx/reader036/viewer/2022082818/56649e7d5503460f94b7f1dc/html5/thumbnails/3.jpg)
CSC proprietary
1. Objectives, Scope, and Assumptions
• Objectives
• Plan and deliver communications and training for xxx stakeholders for <<name of project and releases>>
• Achieve shared understanding of the activities, roles and responsibilities for <<project>> communications and training
Assumptions• <<e.g. A key user network will be established for <<project>>>>• <<e.g. Key users will undertake testing and will provide support to users>>
Summary of <<project and releases>>
Release Date Summary
Or include two short lists covering “in scope” and “out of scope”
![Page 4: CSC proprietary COMMUNICATIONS AND TRAINING PLAN FOR [PROJECT] [date] This template provides an outline structure and suggestions for information to be](https://reader036.vdocuments.mx/reader036/viewer/2022082818/56649e7d5503460f94b7f1dc/html5/thumbnails/4.jpg)
CSC proprietary
2. Audiences
Audiences for <<project>> Communications and Training
The stakeholders identified in the stakeholder analysis are grouped into x audiences based onrole and level of information needed. For example:
1. <<Audience 1>>: Board-level, program, and project sponsorship
2. <<Audience 2>>: Project-impacted users
3. <<Audience 3>>: Those with a broader interest need for awareness
<<Audience 1>>• <<list the roles included>>
<<Audience 2>>• <<list the roles included>>
<<Audience 3>>• <<list the roles included>>
![Page 5: CSC proprietary COMMUNICATIONS AND TRAINING PLAN FOR [PROJECT] [date] This template provides an outline structure and suggestions for information to be](https://reader036.vdocuments.mx/reader036/viewer/2022082818/56649e7d5503460f94b7f1dc/html5/thumbnails/5.jpg)
CSC proprietary
3. Approach
PrinciplesCommunications and training activities to support <<project>> will be:• Pragmatic, using existing vehicles wherever possible• Managed and delivered using the <<project>> common mailbox• Delivered by the Process Owner, Key Users and Project Team (as agreed upon)• Communications will focus on providing high-level orientation information• Training will provide more detailed ‘how to’ guidance
Customize the principles based on project need
![Page 6: CSC proprietary COMMUNICATIONS AND TRAINING PLAN FOR [PROJECT] [date] This template provides an outline structure and suggestions for information to be](https://reader036.vdocuments.mx/reader036/viewer/2022082818/56649e7d5503460f94b7f1dc/html5/thumbnails/6.jpg)
CSC proprietary
3. Approach
Communications ApproachFor release x• <<bullets to summarize the proposed/agreed-upon approach>>
Training ApproachFor release x:• <<bullets to summarize the proposed/agreed-upon approach>>
![Page 7: CSC proprietary COMMUNICATIONS AND TRAINING PLAN FOR [PROJECT] [date] This template provides an outline structure and suggestions for information to be](https://reader036.vdocuments.mx/reader036/viewer/2022082818/56649e7d5503460f94b7f1dc/html5/thumbnails/7.jpg)
CSC proprietary
# Comms/ Training Event
Status Delivery Date Objective / Key Messages
Audience Owner Business ChangeSupportA B C
Date-Month-Quarter
1 User Update Done Email • Confirm plans for training for 2.0 and 2.1• Confirm high-level content of releases 2.1 and 3.0• Planned outage on 11th Dec
x Project Lead/ Process Owner
TBC
2 Invitation to Open Session
Email • Invitation to Open Session• Confirm detailed scope posted in teamroom• Explain go-live date change from 14th to 16th Dec
x Project Lead/ Process Owner
TBC
Date-Month-Quarter
3 User Open Session ATandT • Walkthrough how to sort/filter • Opportunity for user questions
x Project Lead/ Process Owner
TBC
4 Newsletter Update Planned Newsletter • Provide a summary update on project for general audience
x Project Lead/ Process Owner
TBC
5 Outage reminder Email • Reminder of planned outage, [date] x Project Lead/ Process Owner
TBC
6 Go-live Notice (2.1) Email • Confirm go-live as planned• Provide support etc info• Reminder of training dates
x Project Lead/ Process Owner
TBC
7 Training Invite (2.0 and 2.1)
Lotus Notes Invitation
• Email invitations for each session• Include objectives, structure of session
x Process Owner/ Denise
TBC
Date-Month-Quarter
8 Training Reminder Email • Reminder/ arrangements• Link to materials
x Project Lead/ Process Owner
TBC
9 Training Sessions ATandT • Walkthrough role-based scenarios• Including hands-on practice
x Project Lead/ Process Owner
TBC
10 Training Survey and Feedback
Intranet survey via email
• Obtain participant feedback to improve training and understand additional needs
x Project Lead/ Process Owner
TBC
4. Summary communicationsand Training Plan for <<project and release>>Audiences to be updated for each project
![Page 8: CSC proprietary COMMUNICATIONS AND TRAINING PLAN FOR [PROJECT] [date] This template provides an outline structure and suggestions for information to be](https://reader036.vdocuments.mx/reader036/viewer/2022082818/56649e7d5503460f94b7f1dc/html5/thumbnails/8.jpg)
CSC proprietary
5. Communications and Training Roles and Responsibilities
Project Manager: <<enter name>> and Business Process Owner: <<enter name>>
• Provide key information for inclusion in communicationsand training
• (Develop and?) deliver planned communications and training activities
IT Project Manager: <<enter name>>• Provide IT-related key information for inclusion in communications and training
e.g. Confirmation of agreed –upon IT requirements, delivery plan/dates etc..
Development Lead/SME: <<enter name>>• Provide SME/Technical input to communications and training materials
Business Change Management : <<enter name(s)>>• Develop the approach and plans for <<project>> communications and training
• Support the Process Owner in the initial development delivery of communications and training
• Conduct handover to Process Owner
Key User (Names/tbc)• Cascade appropriate communications into their business
• Act as user representative e.g. For testing
Summary of responsibilities directly related to <<project>>
![Page 9: CSC proprietary COMMUNICATIONS AND TRAINING PLAN FOR [PROJECT] [date] This template provides an outline structure and suggestions for information to be](https://reader036.vdocuments.mx/reader036/viewer/2022082818/56649e7d5503460f94b7f1dc/html5/thumbnails/9.jpg)
CSC proprietary
6. Next Steps/ActionsAdd actions with owners and due dates
Ref Activity Owner Due Date
Notes