AWS prescriptive-guidance documentation change
Summary
Updated documentation for application prioritization process, including fixing apostrophes, updating links, changing references to attached templates instead of portfolio playbook templates, minor formatting adjustments, and rephrasing some sections for clarity.
Security assessment
The changes are primarily stylistic (apostrophe corrections), structural (link updates), and procedural (template reference changes). No security vulnerabilities, incidents, or weaknesses are addressed. Security-related sections (e.g., security criteria in complexity scoring) remain unchanged in substance.
Diff
diff --git a/prescriptive-guidance/latest/large-migration-portfolio-playbook/prioritization.md b/prescriptive-guidance/latest/large-migration-portfolio-playbook/prioritization.md index 92eda4fef..a46ba4627 100644 --- a//prescriptive-guidance/latest/large-migration-portfolio-playbook/prioritization.md +++ b//prescriptive-guidance/latest/large-migration-portfolio-playbook/prioritization.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Portfolio playbook for AWS large migrations](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Portfolio playbook for AWS large migrations](introduction.html) @@ -13 +13 @@ About complexity scoring criteriaStep 1: Define the application prioritization p -In a large migration, where you have hundreds of applications lined up for migration, we don’t recommend that you prioritize and plan every application all at once. This is one of the reasons why defining an application prioritization process is critical to a large migration project. To approach the migration in an agile way, you can pick the highest priority applications (3–10 applications), or you can select enough applications for 3–5 waves. You then complete application discovery and wave planning for only the selected applications. This approach saves a significant amount of time because application priority and waves often change during the course of a large migration. +In a large migration, where you have hundreds of applications lined up for migration, we don't recommend that you prioritize and plan every application all at once. This is one of the reasons why defining an application prioritization process is critical to a large migration project. To approach the migration in an agile way, you can pick the highest priority applications (3–10 applications), or you can select enough applications for 3–5 waves. You then complete application discovery and wave planning for only the selected applications. This approach saves a significant amount of time because application priority and waves often change during the course of a large migration. @@ -43 +43 @@ There are two categories of complexity scoring criteria: -You should determine the appropriate scoring criteria for your use case. If you are manually scoring application complexity, in the [portfolio playbook templates](samples/portfolio-playbook-templates.zip), the _Score sheet template for application complexity_ (Microsoft Excel format) contains a standard set of criteria and score values. You might want to start with these values and then customize them for your use case. If you are using a discovery tool for application prioritization, these tools commonly include a standard set of criteria, and you can add, remove, or modify the criteria, and you can weight them according to your needs. When you are establishing criteria, use the questions in the next two sections to help refine your criteria. +You should determine the appropriate scoring criteria for your use case. If you are manually scoring application complexity, the attached _Score sheet template for application complexity_ (Microsoft Excel format) contains a standard set of criteria and score values. You might want to start with these values and then customize them for your use case. If you are using a discovery tool for application prioritization, these tools commonly include a standard set of criteria, and you can add, remove, or modify the criteria, and you can weight them according to your needs. When you are establishing criteria, use the questions in the next two sections to help refine your criteria. @@ -62 +62 @@ Staff availability | During the migration, you might need assistance from the ap - * Will this staff be available to test and validate the application after it’s migrated? + * Will this staff be available to test and validate the application after it's migrated? @@ -80 +80 @@ Readiness | Assess whether the application is ready for migration as follows: -Security | Assess the complexity of the application’s security requirements and security policy as follows: +Security | Assess the complexity of the application's security requirements and security policy as follows: @@ -92 +92 @@ Security | Assess the complexity of the application’s security requirements an -Compliance | Compliance requirements might apply for the application, such as laws, regulations, and guidelines provided by the state, business industry, or company policy. Assess the complexity of the application’s compliance requirements as follows: +Compliance| Compliance requirements might apply for the application, such as laws, regulations, and guidelines provided by the state, business industry, or company policy. Assess the complexity of the application's compliance requirements as follows: @@ -113 +113 @@ Technical criteria | Description -Storage | Assess the application’s current storage as follows: +Storage | Assess the application's current storage as follows: @@ -127 +127 @@ Connectivity | Assess how this application is connected to others in your organi -Application OS and version | Assess the operating system (OS) and version of the application’s server as follows: +Application OS and version| Assess the operating system (OS) and version of the application's server as follows: @@ -129 +129 @@ Application OS and version | Assess the operating system (OS) and version of the - * Is the server’s OS version no longer supported? + * Is the server's OS version no longer supported? @@ -147 +147 @@ Data migration | Assess whether you need to migrate data or files for this appli -Migration strategy | Assess the complexity of the selected migration strategy. For more information about migration strategies, see the [Guide for AWS large migrations](https://docs.aws.amazon.com/prescriptive-guidance/latest/large-migration-guide/). +Migration strategy| Assess the complexity of the selected migration strategy. For more information about the migration strategies, see the [Guide for AWS large migrations](https://docs.aws.amazon.com/prescriptive-guidance/latest/large-migration-guide/). @@ -160 +160 @@ This playbook includes three process options for prioritizing applications. You - * Option 1: Manual complexity scoring – This is a manual prioritization process that can be completed by an individual or in a workshop-style session. In this process, you use complexity scoring criteria to assess the difficulty of migrating each application, which is an important factor in prioritizing applications. This manual process is well-suited to large migrations because it provides a consistent, quantitative approach for prioritizing a large application portfolio. However, evaluating each application against a defined set of criteria can be a slower process when compared with the other two options. + * **Option 1: Manual complexity scoring** – This is a manual prioritization process that can be completed by an individual or in a workshop-style session. In this process, you use complexity scoring criteria to assess the difficulty of migrating each application, which is an important factor in prioritizing applications. This manual process is well-suited to large migrations because it provides a consistent, quantitative approach for prioritizing a large application portfolio. However, evaluating each application against a defined set of criteria can be a slower process when compared with the other two options. @@ -162 +162 @@ This playbook includes three process options for prioritizing applications. You - * Option 2: Application nomination – This is a manual prioritization process that is typically completed a workshop-style session. In this process, the application owners nominate applications for migration. To be successful, this process requires that the application owners have comprehensive knowledge of their respective applications. This process is recommended if time is a factor and you need to quickly prioritize applications. + * **Option 2: Application nomination** – This is a manual prioritization process that is typically completed a workshop-style session. In this process, the application owners nominate applications for migration. To be successful, this process requires that the application owners have comprehensive knowledge of their respective applications. This process is recommended if time is a factor and you need to quickly prioritize applications. @@ -164 +164 @@ This playbook includes three process options for prioritizing applications. You - * Option 3: Discovery tool – This is an automated prioritization process. If the discovery tool in your environment has an automated feature for automated application complexity scoring or prioritization, using this feature can save time and accelerate the application prioritization process. In this process, you typically define criteria within the parameters of the discovery tool, and then the tool analyzes the applications and provides a final complexity score. Before selecting this option, explore the features available in your discovery tool and verify that you can customize it to meet the needs of your use case. + * **Option 3: Discovery tool** – This is an automated prioritization process. If the discovery tool in your environment has an automated feature for automated application complexity scoring or prioritization, using this feature can save time and accelerate the application prioritization process. In this process, you typically define criteria within the parameters of the discovery tool, and then the tool analyzes the applications and provides a final complexity score. Before selecting this option, explore the features available in your discovery tool and verify that you can customize it to meet the needs of your use case. @@ -171 +171 @@ This playbook includes three process options for prioritizing applications. You -In this manual application prioritization process, you use a worksheet to evaluate the application against a defined set of complexity scoring criteria. We recommend that you complete the worksheet in a workshop-style session, or an individual can complete the worksheet by collaborating with stakeholders. You then use the final complexity score and the application prioritization rules in order to determine the application’s priority. Of the manual processes, this provides the most consistent, quantitative approach to determining application complexity and using that information to prioritize applications. +In this manual application prioritization process, you use a worksheet to evaluate the application against a defined set of complexity scoring criteria. We recommend that you complete the worksheet in a workshop-style session, or an individual can complete the worksheet by collaborating with stakeholders. You then use the final complexity score and the application prioritization rules in order to determine the application's priority. Of the manual processes, this provides the most consistent, quantitative approach to determining application complexity and using that information to prioritize applications. @@ -173 +173 @@ In this manual application prioritization process, you use a worksheet to evalua -For the complexity scoring steps in this process, we recommend you use the _Score sheet template for application complexity_ (Excel format), available in the [portfolio playbook templates](samples/portfolio-playbook-templates.zip). This template includes predefined business and technical criteria. You can add, remove, or modify these criteria, or you can adjust the scoring values. For example, you might prefer a scoring range of 1–10 instead of 1–5. Note the following about the provided template: +For the complexity scoring steps in this process, we recommend you use the attached _Score sheet template for application complexity_ (Excel format). This template includes predefined business and technical criteria. You can add, remove, or modify these criteria, or you can adjust the scoring values. For example, you might prefer a scoring range of 1–10 instead of 1–5. Note the following about the provided template: @@ -186 +186 @@ Document your application prioritization process as follows: - 1. In the [portfolio playbook templates](samples/portfolio-playbook-templates.zip), open the _Score sheet template for application complexity_. + 1. Open the attached _Score sheet template for application complexity_. @@ -190 +190 @@ Document your application prioritization process as follows: - * Review the guidance in the About complexity scoring criteria section of this playbook. + 1. Review the guidance in the About complexity scoring criteria section of this playbook. @@ -192 +192 @@ Document your application prioritization process as follows: - * Consider the impact each criterion has to the duration, resources, and cost of the migration. + 2. Consider the impact each criterion has to the duration, resources, and cost of the migration. @@ -194 +194 @@ Document your application prioritization process as follows: - * For a reliable complexity score, include criteria that represent varying levels of migration complexity in your organization. + 3. For a reliable complexity score, include criteria that represent varying levels of migration complexity in your organization. @@ -212 +212 @@ Document your application prioritization process as follows: - 4. Save your application prioritization runbook. + 8. Save your application prioritization runbook. @@ -221 +221 @@ This manual application prioritization process is the easiest and fastest approa -During the nomination process, you enter the nominated applications into the _Score sheet template for application complexity_ (Excel format), included in the [portfolio playbook templates](samples/portfolio-playbook-templates.zip). You will not use all of the scoring and criteria features in this template, but we recommend using this sheet to record the nomination and prioritization decisions. +During the nomination process, you enter the nominated applications into the attached _Score sheet template for application complexity_ (Excel format). You will not use all of the scoring and criteria features in this template, but we recommend using this sheet to record the nomination and prioritization decisions. @@ -246 +246 @@ Document your application prioritization process as follows: -If your discovery tool has a feature for complexity scoring or application prioritization, this automated process requires few resources and can accelerate the application prioritization process. You customize the criteria in the discovery tool for your use case, and then the discovery tool automatically analyzes the applications and provides a final complexity score. Because the tool already has all of the application metadata, you don’t need to enter it. +If your discovery tool has a feature for complexity scoring or application prioritization, this automated process requires few resources and can accelerate the application prioritization process. You customize the criteria in the discovery tool for your use case, and then the discovery tool automatically analyzes the applications and provides a final complexity score. Because the tool already has all of the application metadata, you don't need to enter it. @@ -248 +248 @@ If your discovery tool has a feature for complexity scoring or application prior -For example, the Flexera One Cloud Migration and Modernization (formerly Flexera Foundation and CloudScape) discovery tool has a complexity scoring features called the _Optimization Scorecard_. This feature allows you to select the criteria that you want to include in scoring and weigh each criterion based on your preference. After data discovery is complete, the discovery tool analyzes the data based on the weighted criteria you provided and, using the tool’s proprietary formula, produces the final complexity scores. For more information, see the [Foundation and CloudScape User Guide](https://docs.flexera.com/foundationcloudscape/ug/Content/helplibrary/FoundationCloudscapeRoot.htm) (Flexera documentation) and [Optimization Scorecard](https://docs.flexera.com/foundationcloudscape/ug/Content/helplibrary/FCReports_OptScorecard.htm) (Flexera documentation). +For example, the Flexera One Cloud Migration and Modernization (formerly Flexera Foundation and CloudScape) discovery tool has a complexity scoring features called the _Optimization Scorecard_. This feature allows you to select the criteria that you want to include in scoring and weigh each criterion based on your preference. After data discovery is complete, the discovery tool analyzes the data based on the weighted criteria you provided and, using the tool's proprietary formula, produces the final complexity scores. For more information, see the [Foundation and CloudScape User Guide](https://docs.flexera.com/foundationcloudscape/ug/Content/helplibrary/FoundationCloudscapeRoot.htm) (Flexera documentation) and [Optimization Scorecard](https://docs.flexera.com/foundationcloudscape/ug/Content/helplibrary/FCReports_OptScorecard.htm) (Flexera documentation). @@ -250 +250 @@ For example, the Flexera One Cloud Migration and Modernization (formerly Flexera -The disadvantage of this process is that it requires time (4–8 weeks) to set up the scanning appliance for an agentless discovery tool in your environment or to install agents to all in-scope workloads. Before you can use the scoring feature in your discovery tool, you must allow additional time (4–12 weeks) for the discovery tool to collect metadata by scanning the application workloads and performing application stack analysis. However, you might find that the extra time needed to configure the discovery tool might be recovered by reducing the amount of time and resources needed for metadata collection and application prioritization. For example, if the discovery tool’s data is still current, the portfolio workstream can reuse the discovery tool and its data from the mobilize phase to identify pilot applications. +The disadvantage of this process is that it requires time (4–8 weeks) to set up the scanning appliance for an agentless discovery tool in your environment or to install agents to all in-scope workloads. Before you can use the scoring feature in your discovery tool, you must allow additional time (4–12 weeks) for the discovery tool to collect metadata by scanning the application workloads and performing application stack analysis. However, you might find that the extra time needed to configure the discovery tool might be recovered by reducing the amount of time and resources needed for metadata collection and application prioritization. For example, if the discovery tool's data is still current, the portfolio workstream can reuse the discovery tool and its data from the mobilize phase to identify pilot applications. @@ -260 +260 @@ Document your application prioritization process as follows: - 2. Customize the complexity scoring or application prioritization criteria in your discovery tool according to the instructions for your tool. For more information about selecting criteria, see About complexity scoring criteria. + 2. Customize the complexity scoring or application prioritization criteria in your discovery tool according to the instructions for your tool. For more information about selecting criteria, see _About complexity scoring criteria_. @@ -281 +281 @@ Document your application prioritization process as follows: -In this step, you define _application prioritization rules_ , which help you determine the migration order of the applications. Although an application’s complexity score is an important factor in prioritizing applications and planning waves, business and technology factors also must be considered. You create rules to assess the priority of each application and help you schedule the application in the appropriate wave. Common business and technology rules include: +In this step, you define _application prioritization rules_ , which help you determine the migration order of the applications. Although an application's complexity score is an important factor in prioritizing applications and planning waves, business and technology factors also must be considered. You create rules to assess the priority of each application and help you schedule the application in the appropriate wave. Common business and technology rules include: @@ -354 +354 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Task 2: Defining processes for identifying, collecting, and storing metadata +Task 2: Defining metadata processes