{"id":447,"date":"2022-02-10T19:45:55","date_gmt":"2022-02-10T19:45:55","guid":{"rendered":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/?post_type=chapter&#038;p=447"},"modified":"2022-04-15T19:27:43","modified_gmt":"2022-04-15T19:27:43","slug":"6-3-communications-management-protocol","status":"publish","type":"chapter","link":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/chapter\/6-3-communications-management-protocol\/","title":{"rendered":"6.3 Communications Management Protocol"},"content":{"raw":"The communication management plan should include a protocol that delineates all the critical communication channels for the team and stakeholders, such as the purpose of communication, ICTs utilized, frequency of communications, and types of information to be communicated. An example of a Communications Management Protocol has been provided in Table 6.1 which includes only four purposes of communication.\r\n<table class=\"grid\" style=\"border-collapse: collapse; width: 100%; height: 90px;\" border=\"0\"><caption>Table 6.1. Communications Management Protocol<\/caption>\r\n<tbody>\r\n<tr style=\"height: 18px;\">\r\n<td style=\"width: 20%; height: 18px;\"><strong>Purpose of Communication<\/strong><\/td>\r\n<td style=\"width: 20%; height: 18px;\"><strong>Schedule Frequency<\/strong><\/td>\r\n<td style=\"width: 20%; height: 18px;\"><strong>ICTs or Other Means Utilized<\/strong><\/td>\r\n<td style=\"width: 20%; height: 18px;\"><strong>Types of Information<\/strong><\/td>\r\n<td style=\"width: 20%; height: 18px;\"><strong>Participants: Team Members and Stakeholders<\/strong><\/td>\r\n<\/tr>\r\n<tr style=\"height: 18px;\">\r\n<td style=\"width: 20%; height: 18px;\">Planning<\/td>\r\n<td style=\"width: 20%; height: 18px;\">Every week on Monday<\/td>\r\n<td style=\"width: 20%; height: 18px;\">Microsoft Teams\r\n\r\nZoom\r\n\r\nOneDrive\r\n\r\nEmails<\/td>\r\n<td style=\"width: 20%; height: 18px;\">Requirements\r\n\r\nProject activities\r\n\r\nSchedule\r\n\r\nCost\r\n\r\nRisks and issues<\/td>\r\n<td style=\"width: 20%; height: 18px;\">All the team members<\/td>\r\n<\/tr>\r\n<tr style=\"height: 18px;\">\r\n<td style=\"width: 20%; height: 18px;\">Retrospective<\/td>\r\n<td style=\"width: 20%; height: 18px;\">Every week on Friday<\/td>\r\n<td style=\"width: 20%; height: 18px;\">Microsoft Teams\r\n\r\nZoom\r\n\r\nOneDrive\r\n\r\nEmails<\/td>\r\n<td style=\"width: 20%;\">Status updates\r\n\r\nLessons learned\r\n\r\n&nbsp;<\/td>\r\n<td style=\"width: 20%; height: 18px;\">All the team members<\/td>\r\n<\/tr>\r\n<tr style=\"height: 18px;\">\r\n<td style=\"width: 20%; height: 18px;\">Emergency<\/td>\r\n<td style=\"width: 20%; height: 18px;\">As needed<\/td>\r\n<td style=\"width: 20%; height: 18px;\">Zoom or In-person<\/td>\r\n<td style=\"width: 20%;\">Depends on the reason for emergency<\/td>\r\n<td style=\"width: 20%; height: 18px;\">All the team members<\/td>\r\n<\/tr>\r\n<tr style=\"height: 18px;\">\r\n<td style=\"width: 20%; height: 18px;\">Status updates<\/td>\r\n<td style=\"width: 20%; height: 18px;\">Every week after the retrospective meeting\r\n\r\n<span style=\"font-family: inherit; font-size: inherit;\">Or as needed<\/span><\/td>\r\n<td style=\"width: 20%; height: 18px;\">Emails\r\n\r\nZoom or In-person meetings<\/td>\r\n<td style=\"width: 20%; height: 18px;\">Progress report\r\n\r\nTracking Gantt Chart\r\n\r\nComparison of baselines with the latest situation<\/td>\r\n<td style=\"width: 20%; height: 18px;\">Project sponsor\r\n\r\nClient\r\n\r\nAll team members<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>","rendered":"<p>The communication management plan should include a protocol that delineates all the critical communication channels for the team and stakeholders, such as the purpose of communication, ICTs utilized, frequency of communications, and types of information to be communicated. An example of a Communications Management Protocol has been provided in Table 6.1 which includes only four purposes of communication.<\/p>\n<table class=\"grid\" style=\"border-collapse: collapse; width: 100%; height: 90px;\">\n<caption>Table 6.1. Communications Management Protocol<\/caption>\n<tbody>\n<tr style=\"height: 18px;\">\n<td style=\"width: 20%; height: 18px;\"><strong>Purpose of Communication<\/strong><\/td>\n<td style=\"width: 20%; height: 18px;\"><strong>Schedule Frequency<\/strong><\/td>\n<td style=\"width: 20%; height: 18px;\"><strong>ICTs or Other Means Utilized<\/strong><\/td>\n<td style=\"width: 20%; height: 18px;\"><strong>Types of Information<\/strong><\/td>\n<td style=\"width: 20%; height: 18px;\"><strong>Participants: Team Members and Stakeholders<\/strong><\/td>\n<\/tr>\n<tr style=\"height: 18px;\">\n<td style=\"width: 20%; height: 18px;\">Planning<\/td>\n<td style=\"width: 20%; height: 18px;\">Every week on Monday<\/td>\n<td style=\"width: 20%; height: 18px;\">Microsoft Teams<\/p>\n<p>Zoom<\/p>\n<p>OneDrive<\/p>\n<p>Emails<\/td>\n<td style=\"width: 20%; height: 18px;\">Requirements<\/p>\n<p>Project activities<\/p>\n<p>Schedule<\/p>\n<p>Cost<\/p>\n<p>Risks and issues<\/td>\n<td style=\"width: 20%; height: 18px;\">All the team members<\/td>\n<\/tr>\n<tr style=\"height: 18px;\">\n<td style=\"width: 20%; height: 18px;\">Retrospective<\/td>\n<td style=\"width: 20%; height: 18px;\">Every week on Friday<\/td>\n<td style=\"width: 20%; height: 18px;\">Microsoft Teams<\/p>\n<p>Zoom<\/p>\n<p>OneDrive<\/p>\n<p>Emails<\/td>\n<td style=\"width: 20%;\">Status updates<\/p>\n<p>Lessons learned<\/p>\n<p>&nbsp;<\/td>\n<td style=\"width: 20%; height: 18px;\">All the team members<\/td>\n<\/tr>\n<tr style=\"height: 18px;\">\n<td style=\"width: 20%; height: 18px;\">Emergency<\/td>\n<td style=\"width: 20%; height: 18px;\">As needed<\/td>\n<td style=\"width: 20%; height: 18px;\">Zoom or In-person<\/td>\n<td style=\"width: 20%;\">Depends on the reason for emergency<\/td>\n<td style=\"width: 20%; height: 18px;\">All the team members<\/td>\n<\/tr>\n<tr style=\"height: 18px;\">\n<td style=\"width: 20%; height: 18px;\">Status updates<\/td>\n<td style=\"width: 20%; height: 18px;\">Every week after the retrospective meeting<\/p>\n<p><span style=\"font-family: inherit; font-size: inherit;\">Or as needed<\/span><\/td>\n<td style=\"width: 20%; height: 18px;\">Emails<\/p>\n<p>Zoom or In-person meetings<\/td>\n<td style=\"width: 20%; height: 18px;\">Progress report<\/p>\n<p>Tracking Gantt Chart<\/p>\n<p>Comparison of baselines with the latest situation<\/td>\n<td style=\"width: 20%; height: 18px;\">Project sponsor<\/p>\n<p>Client<\/p>\n<p>All team members<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"author":3,"menu_order":4,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-447","chapter","type-chapter","status-publish","hentry"],"part":439,"_links":{"self":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/pressbooks\/v2\/chapters\/447","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/wp\/v2\/users\/3"}],"version-history":[{"count":6,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/pressbooks\/v2\/chapters\/447\/revisions"}],"predecessor-version":[{"id":839,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/pressbooks\/v2\/chapters\/447\/revisions\/839"}],"part":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/pressbooks\/v2\/parts\/439"}],"metadata":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/pressbooks\/v2\/chapters\/447\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/wp\/v2\/media?parent=447"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/pressbooks\/v2\/chapter-type?post=447"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/wp\/v2\/contributor?post=447"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/wp\/v2\/license?post=447"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}