Organization TravelSafe

Communications Management Plan

Train SmartPass

Date: 13.01.2021
Doc. Version: 1.0.0

Buse Maria-Alexandra, 343A3

Popa Elena, 343A3

Template version: 3.0.1

This artefact template is aligned with the PM² Guide V3.0
For the latest version of the templates visit:
https://www.pm2alliance.eu/publications

The PM² Alliance is committed to the improvement of the PM² Methodology and of its supporting artefact. Project
management best practices and community contributions & corrections are incorporated in the
PM² Alliance’s artefact templates.
Join the PM² Alliance and visit the PM² Alliance GitHub to provide your feedback & contribution:
https://github.com/pm2alliance
 Train SmartPass Communications Management Plan

Document Control Information

Settings Value
Document Title: Communications Management Plan
Project Title: Train SmartPass
Document Author: Buse Maria-Alexandra, Popa Elena
Project Owner (PO): Buse Maria-Alexandra, Popa Elena
Project Manager (PM): Buse Maria-Alexandra, Popa Elena
Doc. Version: 1.0.0
Sensitivity: Limited
Date: 14/01/2021

Document Approver(s) and Reviewer(s):

NOTE: All Approvers are required. Records of each approver must be maintained. All Reviewers in
the list are considered required unless explicitly listed as Optional.
Name Role Action Date
Popa Elena Approve
Buse Maria-Alexandra Review

Document history:
The Document Author is authorized to make the following types of changes to the document without
requiring that the document be re-approved:
• Editorial, formatting, and spelling
• Clarification

To request a change to this document, contact the Document Author or Owner.

Changes to this document are summarized in the following table in reverse chronological order (latest
version first).
Revision Date Created by Short Description of Changes

Configuration Management: Document Location

The latest version of this controlled document is stored in D:\METHODS\PM2\SmartTrainPass\Documents\

Date: 14/01/2021 2 / 17 Doc. Version: 1.0.0

 Train SmartPass Communications Management Plan

TABLE OF CONTENTS
1. INTRODUCTION.....................................................................................................................................4
2. COMMUNICATIONS OBJECTIVES ...........................................................................................................4
2.1. Inputs ..............................................................................................................................................4
2.2. Media ..............................................................................................................................................4
3. PROJECT MEETINGS ..............................................................................................................................5
4. PROJECT REPORTS...............................................................................................................................14
5. OTHER COMMUNICATIONS ............................................... EROARE! MARCAJ ÎN DOCUMENT NEDEFINIT.
6. SUMMARY TABLE ................................................................................................................................15
APPENDIX 1: REFERENCES AND RELATED DOCUMENTS ........ EROARE! MARCAJ ÎN DOCUMENT NEDEFINIT.

Date: 14/01/2021 3 / 17 Doc. Version: 1.0.0

 Train SmartPass Communications Management Plan

1. INTRODUCTION
The Communications Management Plan helps to ensure that all project stakeholders have the
information they need to perform their roles throughout the project. Planning and executing project
communication activities is essential for project success.
The Communications Management Plan determines how to communicate most efficiently and
effectively to the various stakeholders. It defines and documents the communication items content,
format, frequency, the audience and expected results. It also defines how to communicate project
status and the assignment of activities to the various stakeholders, and the communication strategy
for each stakeholder, based on their interests, expectations and influence in the project.

2. COMMUNICATIONS OBJECTIVES
Proactive communication is important on all projects. Communication needs to be:
• Adequate: in the right format and right content;
• Specific: for the targeted audience;
• Sufficient: providing all the necessary information;
• Concise: brief, avoiding repetition and non-important information;
• Timely: addressing points at the right time.

Communication is also a vital way to manage project stakeholders' expectations such as:
• Following project progress and execution;
• Reporting on project quality;
• Assigning activities.

2.1. Inputs
When planning communication, one of the major inputs is the Stakeholder Matrix, in order to identify
project stakeholders' groups. To determine what information needs to be communicated to each
target group the following inputs should be used:
• Project Charter
• Project Handbook and possible related management plans
• Project Work Plan.

2.2. Media
The communication media that will be used for the project are:
• Email(s);
• Document(s) (MS Word and/or PowerPoint…);
• Phone call(s);
• Meeting(s) (using, meeting rooms, conference phones, video rooms…);

The communication media above contain, or are supported by:

• Minutes of Meeting (MoM);
• The Project Status Report;
• The Project Progress Report;

Date: 14/01/2021 4 / 17 Doc. Version: 1.0.0

 Train SmartPass Communications Management Plan

• The Quality Review Report;

• Contractor Status Report;
• Custom or Ad-Hoc Reports;
• Project Work Plan (updated estimates of effort and schedule);
• Project Logs;
• Project repository;

3. PROJECT MEETINGS
In this section the following meetings are described:
• Planning Kick-off Meeting
• Executing Kick-off Meeting
• Project Status Meeting
• Project Core Team (PCT) Meeting
• Project Review Meeting
• Project Steering Committee (PSC) Meeting
• Change Control Meeting
• Project-End Review Meeting

Date: 14/01/2021 5 / 17 Doc. Version: 1.0.0

 Train SmartPass Communications Management Plan

MEETING Planning Kick-off Meeting

Purpose Official kick-off of the planning phase of the project. After this meeting, the
scope of the project as well as the project governance structure must be
clear, the expectations of all the key project stakeholders and their roles &
responsibilities must be set and all the relevant risks at the time must be
identified.
Location Defined by the Project Manager (PM) in time.
Frequency Done once at project level. Date of the meeting to be defined.
Chairperson Project Manager (PM)
Minutes by To be defined by the Project Manager (PM).
Attendees Project Owner (PO)
Business Manager (BM)
Solution Provider (SP)
Project Manager (PM)
Project Core Team (PCT)
Business Implementation Group (BIG)
User Representatives (URs) – Reprezentanti ai companiilor de transport
feroviar
Agenda Items • Introduce the agenda;
• Introduce participants;
• Outline the goals, expectations and activities of the Planning Phase, and
discuss the planning timeline;
• Introduce the project scope statement;
• Invite the Project Owner (PO) to explain the importance of the project for
the organisation and other beneficiaries;
• Discuss the main elements of the Project Charter;
• Discuss the governance structure, roles & responsibilities of the Project
Core Team (PCT) and the Business Implementation Group (BIG);
• Discuss the overall project timeline;
• Discuss the overall approach of the project;
• Discuss the project plans needed for the project;
• Discuss risks, constraints and assumptions;
• Discuss or present any project supporting tools;
• Allow time for any other business (questions & answers);
• Summarise the discussion (decisions, actions, and risk);
• Communicate the next steps.
Distribution list All participants invited.
Media Meeting minutes written in MS-Word or by email.

Date: 14/01/2021 6 / 17 Doc. Version: 1.0.0

 Train SmartPass Communications Management Plan

MEETING Executing Kick-off Meeting

Purpose Official kick-off of the executing phase of the project. After this meeting, the
Project Core Team (PCT) is aware of the scope of the project, the project
governance structure, the roles & responsibilities of the team members as
well as the project rules.
Location Defined by the Project Manager (PM) in time.
Frequency Done once at project level or for each major project phase. Date of the
meeting to be defined.
Chairperson Project Manager (PM)
Minutes by To be defined by the Project Manager (PM).
Attendees Project Owner (PO) (may be represented by the Business Manager)
Business Manager (BM)
Project Manager (PM)
Project Core Team (PCT)
Agenda Items • Introduce the agenda;
• Introduce participants;
• Present the Project Work Plan;
• Present the Communications Management Plan;
• Agree on the conflict resolution process and present the escalation
procedure;
• Present the Risk Management, Issue Management and Project Change
Management processes, and the Quality Assurance & Control activities;
• Clarify the expectations for the Project Core Team (PCT);
• Agree on the team’s ground rules (communication via email, meetings,
phone, meeting minutes to be produced, availability, etc.);
• Allow time for any other business (questions & answers);
• Summarise the discussion (decisions, actions, and risk).
Distribution list All participants invited.
Media Meeting minutes written in MS-Word or by email.

Date: 14/01/2021 7 / 17 Doc. Version: 1.0.0

 Train SmartPass Communications Management Plan

MEETING Project Status Meeting

Purpose • Discuss Project status;
• Discuss open actions and check progress;
• Discuss new risks or/and issues and define action points
• Discuss and resolve conflicts;
• Discuss and review change requests and possibly approve/reject.
Location Office of Project Manager (PM) (or meeting room to be defined in time).
Frequency O data la 2 saptamani, Vineri
Chairperson Project Manager (PM) (or delegated person if Project Manager (PM) cannot
attend) or Project Manager Assistant (PMA)(s).
Minutes by Rapoarte cu statusul activitatilor intrunite de fiecare Team Leader
Attendees Project Owner (PO)
Business Manager (BM)
Project Manager (PM)
(Functional) Team Leader
Agenda Items Progress status review (presentation of periodic Project Status report);
• Accomplishments (Current and Planned actions);
• Actual work (m.d.) vs Planned (m.d.);
• Milestones status;
• Current deliverables status:
o Indicators;
o Existing change requests (current progress);
o New change requests (input from Project Steering Committee).
• Next deliverables status:
o Existing change requests (Current progress);
o New change requests (input from Project Steering Committee).
• Risks & Issues:
o Major risks, issues & actions monitoring.
Distribution list All participants invited.
Media • Project Status Report will be written in MS-Word document, and sent by
e-mail; and/or
• Meeting minutes written in e-mail.

Date: 14/01/2021 8 / 17 Doc. Version: 1.0.0

 Train SmartPass Communications Management Plan

MEETING Project Core Team (PCT) Meeting

Purpose • Obtain commitment on the execution tasks;
• Review the accomplished work and estimate time to complete +
schedule;
• Review risk & issues;
• Assess new change requests.
Location Office of the (Functional) Team Leader (or meeting room to be defined in
time).
Frequency Saptamanal, ziua de Vineri
Chairperson (Functional) Team Leader
Minutes by Minutes will be made by the (Functional) Team Leader (or delegated
person).
Attendees All Project Core Team (PCT) members working on the project.
Agenda Items Project status:
• Current and next milestones;
• Done;
• To do;
• Estimate Time to Completion review;
• Plan reviews;
• Indicators review.
Process status:
• Debriefing on quality assurance aspects.
Risk & Issues:
• Risks, issues & actions monitoring.
Change management:
• Assess new change requests.
Distribution list (Functional) Team Leader
Project Manager (PM)
Project Core Team (PCT) members working on the project.
Media • Updated project plans;
• Estimate Time to Complete updated for every task in Project Work Plan;
• Updated Change Log with assessment results;
• Meeting minutes (if used): written in an email or MS-Word document.

Date: 14/01/2021 9 / 17 Doc. Version: 1.0.0

 Train SmartPass Communications Management Plan

MEETING Project Review Meeting

Purpose • Management Review meeting;
• Meeting discussing about project progress.
• Topics to be discussed: major scope changes, next year’s budget, major
re-baselining of the Project Work Plan (PWP), confirming alignment to
portfolio goals and objectives, and business strategies.
Location No specific location. Defined by the (Functional) Team Leader in time.
Frequency O data la 3 luni
Chairperson Project Manager (PM)
Minutes by Project Support Officer (or delegated person)
Attendees Project Steering Committee (PSC) members
(Functional) Team Leader
Project Support Officer
Agenda Items • Follow-up of mandatory documents;
• Major milestones review;
• Testing progress;
• Risks (budget, resources, others), issues & actions monitoring;
• Project Manager (PM) feedback;
• Others: people / resources / contracts.
Distribution list All participants invited.
Media • Project Progress Report.
• Meeting minutes in MS-Word, and sent by e-mail.

Date: 14/01/2021 10 / 17 Doc. Version: 1.0.0

 Train SmartPass Communications Management Plan

MEETING Project Steering Committee Meeting

Purpose • Meeting with the sponsor(s) about the status and follow-up of the
project;
• This meeting has also to be held at the moment there are:
− Contractual aspects to be discussed;
− Formal project approvals requested
− Commitments made.
Location No specific location. Defined by Project Owner (PO) in time.
Frequency Monthly or at the moment there is an important project milestone reached,
that needs approval(s) from Sponsor(s).
Chairperson Project Owner (PO)
Minutes by Business Manager (BM)
Attendees Project Steering Committee (PSC):
• Solution Provider (SP)
• Project Owner (PO)
• Business Manager (BM)
• Project Manager (PM)
Agenda Items Project debriefing:
• Accomplishments for this period;
• Problems encountered and actions taken;
• Major points meriting management attention;
• Subjects to be realised until next milestone/meeting;
• Evaluation of current status with respect to project scope, project budget,
project finish date;
• Formal approvals / Commitments / Contractual aspects.
Distribution list All participants invited.
Media • Meeting minutes written in MS-Word, and sent by e-mail;
• Decision log updated;

Date: 14/01/2021 11 / 17 Doc. Version: 1.0.0

 Train SmartPass Communications Management Plan

MEETING Change Control Meeting

Purpose • Discuss and prioritise change requests or client's inquiries;
• Discuss and prioritise maintenance requests;
• Prepare for decisions to be made by the Project Steering Committee (PSC)
or the Change Control Board (CCB) or Change Advisory Board (CAB).
Location Office of Project Manager (PM) (or meeting room to be defined in time)
Frequency Lunar

Chairperson Project Manager (PM) (or delegated person if Project Manager (PM) cannot
attend) or Project Manager Assistant (PMA) that are part of the Project.
Minutes by Project Manager
Attendees Business Manager (BM)
Project Manager (PM)
Agenda Change requests status:
1- Progress update on open changes
Current deliverables status:
2- Existing change requests (current progress)
3- New change requests (commitment on prioritization, on budget, on
milestones, …)
Next deliverables status:
4- Existing change requests (current progress)
5- New change requests (commitment on prioritization, on budget, on
milestones, …)
Distribution list All participants invited.
Media • Meeting minutes written in MS-Word and sent by e-mail(s);
• Change log to be updated.

Date: 14/01/2021 12 / 17 Doc. Version: 1.0.0

 Train SmartPass Communications Management Plan

MEETING
Project-End Review Meeting
Purpose The objectives for the Project-End Review meeting are:
• Review the project performance and main achievements;
• Discuss the overall project experience;
• Discuss if the objectives have been reached and if not, why;
• Discuss problems and challenges faced during project and the way
they were addressed;
• Discuss Lessons Learned and Best Practices that might be useful for
future projects.
Location No specific location. Defined by the Project Manager (PM) in time.
Frequency No frequency. The meeting is realized once per project or major project
phase.
Chairperson Project Manager (PM)
Minutes by To be defined by Project Manager (PM) in time.
Attendees Project Owner (PO)
Business Manager (BM)
Solution Provider (SP)
Project Manager (PM)
User Representatives
(Functional) Team Leader
Agenda Items • Review the project performance and achievements;
• Evaluate project relevant facts (budget & work history, milestones &
timing history, technical & methodological approaches used);
• Identify the Lessons learned;
• Business Implementation plan (change management, how to achieve
desired outcomes and benefits)
Distribution list All participants invited.
Media Project-End Review MoM, Project-End Report Word Document; sent by e-
mail.

Date: 14/01/2021 13 / 17 Doc. Version: 1.0.0

4. PROJECT REPORTS
Reports may be produced to show the status of the project or a particular work package or the collected required measurements etc. This section should
document how the reports will be distributed and the standard format for the project reports.
The following reports are described in this section:
• Project Status Report
• Project Progress Report
• Project-End Report

REPORT Project Status Report

Purpose The Project Status Report provides summary information regarding the overall project performance (rather than
detailed task-level information), in one page with traffic light visualisation of the major project parameters as cost,
schedule, scope/changes, risks, issues. This document reports on the status of important milestones for the current
reporting period and provides forecasts for future performing periods.
Frequency The elaboration of this report will follow the frequency defined for the Project Status Meeting.
Author Project Manager (PM)
Distributed to Refer to Distribution List specified in the Project Status Meeting.
Media Word Document
Reference to <Please reference to the document.>

REPORT Project Progress Report

Purpose The Project Progress Report provides a high-level overview of the entire project and its actual status. The report
includes a Project Overview (Project Stakeholders, Milestones and Deliverables, Project Plan, Budget and Costs) and
further Project Details (Scope Changes, Major Risks/Issues and Actions Taken, Achievements). This report provides more
detail than the Project Status Report.
Frequency The elaboration of this report will follow the frequency defined for the Project Review Meeting.
Author Project Manager (PM)
Distributed to Refer to Distribution List specified in the Project Progress Review Meeting.
Media Word Document
Reference to <Please reference to the document.>

Date: 14/01/2021 14 / 17 Doc. Version: 1.0.0

 REPORT
Project-End Report
Purpose The Project-End Report summarises project experience. The evaluation of the major project parameters, best practices,
lessons learned, pitfalls and solutions to problems are documented in this report.
Frequency This report is realised once, during the Closing Phase.
Author Project Manager (PM)
Distributed to Refer to Distribution List specified in the definition of Project-End Review Meeting.
Media Word Document
Reference to <Please reference to the document.>

5. SUMMARY TABLE

Item Name Audience (summary) Responsible person Frequency Media of

Communication
Planning Kick-off Project Owner (PO) Project Manager (PM) Once at Project Level. Meeting and
Meeting Business Manager (BM) Meeting minutes
Solution Provider (SP)
Project Manager (PM)
Project Core Team (PCT)
Business Implementation Group
(BIG)
User Representatives (URs)
Executing Kick- Project Owner (PO) Project Manager (PM) Once at Project Level or for each major Meeting and
off Meeting Business Manager (BM) project phase. Meeting minutes
Project Manager (PM)
Project Core Team (PCT)
Project Status Project Owner (PO) Project Manager (PM) or O data la 2 saptamani, Vineri Meeting minutes
Meeting Business Manager (BM) Project Manager (PMA)(s) and
Project Manager (PM) Project Status
(Functional) Team Leader Report.

Date: 14/01/2021 15 / 17 Doc. Version: 1.0.0

 Item Name Audience (summary) Responsible person Frequency Media of
Communication
Project Core All Project Core Team (PCT) (Functional) Team Leader Saptamanal, Vineri Meeting minutes
Team (PCT) members working on the project. Updated Change
Meeting log
Updated project
plans with actuals
Estimate Time to
Complete updated.
Project Review Project Manager (PM) Project Manager (PM) Quarterly (or more frequently, depending Meeting minutes
Meeting Solution Provider (SP) (optional) on project duration). Project Progress
(Functional) Team Leader Report
Project Support Officer

Project Steering Solution Provider (SP) Project Owner (PO) Monthly or at the moment there is an Meeting minutes
Committee (PSC) Project Steering Committee (PSC) important project milestone reached, Decision log
Meeting members that needs approval(s) from Sponsor(s). updated
Change Control Business Manager (BM) Project Manager (PM) Lunar Meeting
Meeting Project Manager (PM)
Other project roles or stakeholders Meeting minutes
(optional). Change log
(updated)
Project-End Project Owner (PO) Project Manager (PM) Once per project or major project phase. Meeting minutes
Review Meeting Business Manager (BM) Project-End Report
Solution Provider (SP)
Project Manager (PM)
User Representatives (URs)
(Functional) Team Leader
Project Core Team (PCT) Other
project roles or stakeholders
(optional).
Project Status Refer to Audience specified in the Project Manager (PM) Will follow the frequency defined for the Word document
Report Project Status Meeting. Project Status Meeting.
Project Progress Refer to Audience specified for the Project Manager (PM) will follow the frequency defined for the Word document
Report Project Review Meeting. Project Review Meeting.
Date: 14/01/2021 16 / 17 Doc. Version: 1.0.0
 Item Name Audience (summary) Responsible person Frequency Media of
Communication
Project-End Refer to Audience specified in the Project Manager (PM) Once, during the Project Closing Phase. Word Document
Report Project-End Review Meeting.
,

Date: 14/01/2021 17 / 17 Doc. Version: 1.0.0