AWS prescriptive-guidance documentation change
Summary
Updated communication plan documentation with editorial changes: fixed apostrophes, reordered steps, improved meeting descriptions, updated templates reference, and enhanced table formatting.
Security assessment
Changes are editorial improvements and organizational updates without any security-specific content. The modifications focus on communication procedures, meeting structures, and template references, with no evidence of addressing vulnerabilities, security incidents, or security features.
Diff
diff --git a/prescriptive-guidance/latest/large-migration-governance-playbook/task-communication-plan.md b/prescriptive-guidance/latest/large-migration-governance-playbook/task-communication-plan.md index d36da0a1b..99dc7054f 100644 --- a//prescriptive-guidance/latest/large-migration-governance-playbook/task-communication-plan.md +++ b//prescriptive-guidance/latest/large-migration-governance-playbook/task-communication-plan.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Project governance playbook for AWS large migrations](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Project governance playbook for AWS large migrations](introduction.html) @@ -11 +11 @@ Step 1: Create a communications teamStep 2: Establish an escalation planStep 3: -A critical element of the governance model is identifying who is responsible for communicating with application owners and how to escalate if an application owner doesn’t respond. In this task, you define who is responsible for communications, determine what the regular communications and meetings will be, create your standard communication templates, and determine what happens if you need to escalate an issue. +A critical element of the governance model is identifying who is responsible for communicating with application owners and how to escalate if an application owner doesn't respond. In this task, you define who is responsible for communications, determine what the regular communications and meetings will be, create your standard communication templates, and determine what happens if you need to escalate an issue. @@ -17 +17 @@ In this task, you do the following: - * Step 2: Establish an escalation plan + * Step 2: Define meetings and their cadence @@ -19 +19 @@ In this task, you do the following: - * Step 3: Define meetings and their cadence + * Step 3: Establish an escalation plan @@ -21 +21 @@ In this task, you do the following: - * Step 4: Prepare meeting presentations + * Step 4: Prepare meeting presentations and communication tools @@ -45 +45 @@ Do the following: -When an issue arises in the migration, you must be able to quickly resolve it. By defining an escalation plan before the migration starts, you can provide a clear action plan to the team in advance, which helps prevent delay, frustration, or surprises. We recommend specifying a single-threaded leader for each business unit. If an application owner isn’t engaging or responding, you can escalate to that individual. +When an issue arises in the migration, you must be able to quickly resolve it. By defining an escalation plan before the migration starts, you can provide a clear action plan to the team in advance, which helps prevent delay, frustration, or surprises. We recommend specifying a single-threaded leader for each business unit. If an application owner isn't engaging or responding, you can escalate to that individual. @@ -47 +47 @@ When an issue arises in the migration, you must be able to quickly resolve it. B -This step is typically completed by the project manager and project sponsor. When establishing the escalation plan, you need to define the type of issue, the circumstances in which you should escalate the issue (known as the _trigger_), and define the tiers of escalation. We recommend no more than three tiers. For each tier, you should identify the _audience_ , or _response owner_ , and the amount of time that the audience has to respond. For example, if the first escalation audience doesn’t resolve the issue within 24 hours, escalate the issue to the second tier, which is a different audience. With each escalation, CC the audiences of any prior tiers. +This step is typically completed by the project manager and project sponsor. When establishing the escalation plan, you need to define the type of issue, the circumstances in which you should escalate the issue (known as the _trigger_), and define the tiers of escalation. We recommend no more than three tiers. For each tier, you should identify the _audience_ , or _response owner_ , and the amount of time that the audience has to respond. For example, if the first escalation audience doesn't resolve the issue within 24 hours, escalate the issue to the second tier, which is a different audience. With each escalation, CC the audiences of any prior tiers. @@ -70 +70,3 @@ Do the following: -**#** | **Issue** | **Trigger** | **Tier 1** | **Tier 2** | **Tier 3** +The following is an example of how you might record an issue in the escalation plan. + +#| Issue| Trigger| Tier 1| Tier 2| Tier 3 @@ -72,2 +74,2 @@ Do the following: -_Audience_ | _Escalate after_ | _Audience_ | _Escalate after_ | _Audience_ -1 | Firewall ports need to be open to migrate workloads to AWS | Firewall isn’t open by T-28 commit meeting | Network team, migration lead | 24 hours | Network team manager | 24 hours | Executive team, lead of impacted business unit +**Audience**| **Escalate after**| **Audience**| **Escalate after**| **Audience** +1| Firewall ports need to be open to migrate workloads to AWS| Firewall isn't open by T-28 commit meeting| Network team, migration lead| 24 hours| Network team manager| 24 hours| Executive team, lead of impacted business unit @@ -81 +83 @@ The following recurring meetings are common in a large migration project: - 1. Steering committee meetings – These meetings are typically held twice a month, and the objective is to share the project status and resolve any issues that require involvement from executive leadership. Participants of this meeting typically include the project sponsor, executive leadership, and a representative from the project management office. + * **Steering committee meetings** – These meetings are typically held twice a month, and the objective is to share the project status and resolve any issues that require involvement from executive leadership. Participants of this meeting typically include the project sponsor, executive leadership, and a representative from the project management office. @@ -83 +85 @@ The following recurring meetings are common in a large migration project: - 2. Project status review meetings – These meetings are typically held once per week. The objective is to review the project status at the workstream level and evaluate the need for resources or subject matter experts. Participants of this meeting include the project manager, project stakeholders, workstream owners, and the migration lead. + * **Project status review meetings** – These meetings are typically held once per week. The objective is to review the project status at the workstream level and evaluate the need for resources or subject matter experts. Participants of this meeting include the project manager, project stakeholders, workstream owners, and the migration lead. @@ -85 +87 @@ The following recurring meetings are common in a large migration project: - 3. Daily stand-ups – These are very short meetings held once per day. It is called a stand-up because the meeting should be short enough that the participants don’t require a chair. The purpose is to review planned and recently completed tasks and surface any issues. In daily stand-ups, you typically use a visual task management tool, such as a Kanban board or Gantt chart, which you determine in [Step 1: Select a project management tool](./task-project-management.html#step-pm-tool). + * **Daily stand-ups** – These are very short meetings held once per day. It is called a _stand-up_ because the meeting should be short enough that the participants don't require a chair. The purpose is to review planned and recently completed tasks and surface any issues. In daily stand-ups, you typically use a visual task management tool, such as a Kanban board or Gantt chart, which you determine in [Step 1: Select a project management tool](./task-project-management.html#step-pm-tool). @@ -87 +89 @@ The following recurring meetings are common in a large migration project: - 4. Infrastructure and operations checkpoint meetings – These meetings are usually held twice a week. The objective is to review the progress of the migration, review active issues and decide whether escalation is required, collaborate across workstreams, and plan resources for the next sprint. Participants of this meeting include the technical team members who own RACI-defined migration activities. + * **Infrastructure and operations checkpoint meetings** – These meetings are usually held twice a week. The objective is to review the progress of the migration, review active issues and decide whether escalation is required, collaborate across workstreams, and plan resources for the next sprint. Participants of this meeting include the technical team members who own RACI-defined migration activities. @@ -89 +91 @@ The following recurring meetings are common in a large migration project: - 5. Migration business hours – This time is reserved as an open meeting for application owners to seek support or guidance. We recommend that you hold business hours three times per week. + * **Migration business hours** – This time is reserved as an open meeting for application owners to seek support or guidance. We recommend that you hold business hours three times per week. @@ -94 +96 @@ The following recurring meetings are common in a large migration project: -We recommend starting with the _Meeting plan template_ (Microsoft Excel format) available in the [project governance playbook templates](samples/project-governance-playbook-templates.zip). This template contains a default example, and you can customize it for your project. +We recommend starting with the attached _Meeting plan template_ (Microsoft Excel format). This template contains a default example, and you can customize it for your project. @@ -100 +102 @@ As defined in Step 3: Define meetings and their cadence, large migrations requir -We recommend starting with the following templates, which are included in the [project governance playbook templates](samples/project-governance-playbook-templates.zip): +We recommend starting with the following attached templates: @@ -102 +104 @@ We recommend starting with the following templates, which are included in the [p - * _Status report template (Microsoft PowerPoint format)_ + * _Status report template_ (Microsoft PowerPoint format) @@ -132 +134 @@ Do the following: -If you completed the mobilize phase, you might have already established some of the meetings in this step. Complete this step for any meetings that you haven’t already scheduled. According to the meeting plan you developed in Step 3: Define meetings and their cadence, the meeting owner should schedule the following recurring meetings: +If you completed the mobilize phase, you might have already established some of the meetings in this step. Complete this step for any meetings that you haven't already scheduled. According to the meeting plan you developed in Step 3: Define meetings and their cadence, the meeting owner should schedule the following recurring meetings: @@ -164 +166 @@ Understanding the change management process for your organization is critical to -All migration leads should understand the change management process prior to discovery activities. Some migration-related tasks require approval, and team members need to understand their responsibilities in the change management process. For more information about training, see [Training and skills required for large migrations](https://docs.aws.amazon.com/prescriptive-guidance/latest/large-migration-foundation-playbook/training-skills.html) in the _Foundation playbook for AWS large migrations._ +All migration leads should understand the change management process prior to discovery activities. Some migration-related tasks require approval, and team members need to understand their responsibilities in the change management process. For more information about training, see [Training and skills required for large migrations](https://docs.aws.amazon.com/prescriptive-guidance/latest/large-migration-foundation-playbook/training-skills.html) in the _Foundation playbook for AWS large migrations_. @@ -195 +197 @@ Task: Kicking off the migrate phase -Task: Defining communication gates +Task: Defining communication gates and schedules