AWS prescriptive-guidance documentation change
Summary
Updated navigation links, expanded step descriptions, improved RACI matrix documentation, restructured backup strategy guidance, fixed apostrophes in contractions, updated template references to 'attached', corrected typo in RAID log section, and expanded task/stage titles.
Security assessment
The changes focus on project management processes without addressing specific vulnerabilities. The mention of backup/disaster recovery strategies is operational guidance, not a security fix. The financial data storage recommendation is a general best practice without evidence of addressing a specific security incident.
Diff
diff --git a/prescriptive-guidance/latest/large-migration-governance-playbook/task-project-management.md b/prescriptive-guidance/latest/large-migration-governance-playbook/task-project-management.md index 2ad72d1f9..929685b0b 100644 --- a//prescriptive-guidance/latest/large-migration-governance-playbook/task-project-management.md +++ b//prescriptive-guidance/latest/large-migration-governance-playbook/task-project-management.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) @@ -7 +7 @@ -Step 1: Select a project management toolStep 2: Validate roles and responsibilitiesStep 3: Establish a benefit-tracking officeStep 4: Create a project summary dashboardStep 5: Create a financial reporting processStep 6: Create a resource planStep 7: Create a decision logStep 8: Create a RAID logTask exit criteria +Step 1: Select a project management toolStep 2: Validate roles and responsibilities for all migration activitiesStep 3: Establish a benefit-tracking officeStep 4: Create a project summary dashboardStep 5: Create a financial reporting processStep 6: Determine how to manage and scale resourcesStep 7: Create a decision logStep 8: Create a RAID logTask exit criteria @@ -53 +53 @@ For more information about how these tools are used, see [Establishing an agile -In the [Foundation playbook for AWS large migrations](https://docs.aws.amazon.com/prescriptive-guidance/latest/large-migration-foundation-playbook/), you created a detailed RACI matrix for each migration strategy and high-level task in your large migration project. A RACI matrix is a responsibility assignment tool, and the name is derived from the four responsibility types defined in the matrix: responsible (R), accountable (A), consulted (C), and informed (I). This matrix format is recommended to align roles and responsibilities across all of the migration activities. This matrix can align on-site teams with remote teams or external partners. In this step, you validate the matrices are correct and review them with the project teams. +In the [Foundation playbook for AWS large migrations](https://docs.aws.amazon.com/prescriptive-guidance/latest/large-migration-foundation-playbook/), you created a detailed RACI matrix for each migration strategy and high-level task in your large migration project. A _RACI matrix_ is a responsibility assignment tool, and the name is derived from the four responsibility types defined in the matrix: responsible (R), accountable (A), consulted (C), and informed (I). This matrix format is recommended to align roles and responsibilities across all of the migration activities. This matrix can align on-site teams with remote teams or external partners. In this step, you validate the matrices are correct and review them with the project teams. @@ -57,5 +57 @@ In order to tailor the RACI tasks for your organization, we recommend you consid - * Understand the change management processes, the lead times required for those processes, and the roles involved in approving changes. For more information, see [Step 6: Understand the change management process](./task-communication-plan.html#step-change-management). - - * Make sure that you have vetted your back-up and disaster recovery strategy prior to starting the migration, and share this strategy with the migration team. If you identify gaps in the strategy, we recommend you use integrated cloud services, such as AWS Backup or CloudEndure Disaster Recovery. - - +Understand the change management processes, the lead times required for those processes, and the roles involved in approving changes. For more information, see [Step 6: Understand the change management process](./task-communication-plan.html#step-change-management). @@ -62,0 +59 @@ In order to tailor the RACI tasks for your organization, we recommend you consid +Make sure that you have vetted your back-up and disaster recovery strategy prior to starting the migration, and share this strategy with the migration team. If you identify gaps in the strategy, we recommend you use integrated cloud services, such as AWS Backup or CloudEndure Disaster Recovery. @@ -66 +63 @@ Do the following: - 1. If you haven’t done so already, create a RACI matrix for each high-level task according to the instructions in the [Foundation playbook for AWS large migrations](https://docs.aws.amazon.com/prescriptive-guidance/latest/large-migration-foundation-playbook/). + 1. If you haven't done so already, create a RACI matrix for each high-level task according to the instructions in the [Foundation playbook for AWS large migrations](https://docs.aws.amazon.com/prescriptive-guidance/latest/large-migration-foundation-playbook/). @@ -92 +89 @@ In each meeting, this team usually reviews and answers the following questions: -If the benefit-tracking office determines that the migration isn’t achieving the desired velocity, this team should recommend adjustments to process, resourcing, or communications plans. +If the benefit-tracking office determines that the migration isn't achieving the desired velocity, this team should recommend adjustments to process, resourcing, or communications plans. @@ -126 +123 @@ The project team must work with key project stakeholders collectively to develop -We recommend starting with the _Project summary dashboard template_ (Microsoft PowerPoint format), available in the [project governance playbook templates](samples/project-governance-playbook-templates.zip). Do the following: +We recommend starting with the attached _Project summary dashboard template_ (Microsoft PowerPoint format). Do the following: @@ -141 +138 @@ Typically, you track financial reporting separately from the project status repo -We recommend starting with the _Financial glide path template_ (Microsoft PowerPoint format), available in the [project governance playbook templates](samples/project-governance-playbook-templates.zip). Do the following: +We recommend starting with the attached _Financial glide path template_ (Microsoft PowerPoint format). Do the following: @@ -153 +150 @@ We recommend starting with the _Financial glide path template_ (Microsoft PowerP - 6. Determine where you will save this financial report. Because it contains sensitive financial information, we don’t recommend saving this template in the shared repository with the rest of the project documentation. + 6. Determine where you will save this financial report. Because it contains sensitive financial information, we don't recommend saving this template in the shared repository with the rest of the project documentation. @@ -164 +161 @@ The resource plan is different for each large migration, and it is typically det -When planning resources, consider the migration strategies for your portfolio and how these affect your migration and portfolio teams. For example, rehost is a common strategy for large migrations because it is low complexity. Almost every large migration project has at least one rehost migration pod of 4–5 individuals. If you plan to include high-complexity migration strategies, such as replatform or refactor, you should create migration team pods for these strategies and include additional migration and portfolio team resources in your resource plan. For more information about workstreams, team structure, and how many people are needed for each pod, see [Team organization and composition](https://docs.aws.amazon.com/prescriptive-guidance/latest/large-migration-foundation-playbook/team-org.html) in the _Foundation playbook for AWS large migrations_. +When planning resources, consider the migration strategies for your portfolio and how these affect your migration and portfolio teams. For example, rehost is a common strategy for large migrations because it is low complexity. Almost every large migration project has at least one rehost migration pod of 4–5 individuals. If you plan to include high-complexity migration strategies, such as replatform or refactor, you should create migration team pods for these strategies and include additional migration and portfolio team resources in your resource plan. For more information about workstreams, team structure, and how many people are needed for each pod, see [Team organization and composition](https://docs.aws.amazon.com/prescriptive-guidance/latest/large-migration-foundation-playbook/team-org.html) in the _Foundation playbook for AWS large migrations_. @@ -260 +257 @@ Do the following: - 4. Before each project status review meeting, review the log for any risks and issues identified since the previous meeting, and include these in your _project status report presentation_. This ensures project-level transparency for all risks and issues. + 4. Before each project status review meeting, review the log for any risks and issues identified since the previous meeting, and include these in your _project status report_ presentation. This ensures project-level transparency for all risks and issues. @@ -294 +291 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Task: Defining communication gates +Task: Defining communication gates and schedules @@ -296 +293 @@ Task: Defining communication gates -Stage 2: Implementing +Stage 2: Implementing a large migration