AWS prescriptive-guidance documentation change
Summary
Expanded documentation for operations integration phases (discovery, design, implementation) with added details about activities, deliverables, and organizational preparation. Updated section headers, navigation links, and diagram references.
Security assessment
Added 'risk assessment and mitigation strategies' as a key activity in the Design phase, which relates to security practices. However, there's no evidence this addresses a specific security vulnerability or incident. The change enhances documentation of security-related processes but doesn't reference any specific security issue resolution.
Diff
diff --git a/prescriptive-guidance/latest/migration-operations-integration/guidelines-steps.md b/prescriptive-guidance/latest/migration-operations-integration/guidelines-steps.md index c36ba3f6a..2014b2d92 100644 --- a//prescriptive-guidance/latest/migration-operations-integration/guidelines-steps.md +++ b//prescriptive-guidance/latest/migration-operations-integration/guidelines-steps.md @@ -3 +3,3 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Modernizing operations in the AWS Cloud](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Modernizing operations in the AWS Cloud](introduction.html) + +Discovery phaseDesign phaseImplementation phase @@ -7 +9,3 @@ -The three primary phases are discovery, design, and implementation. This section covers inputs required from other workstreams and outputs expected from each phase. +The three primary phases during OI are discovery, design, and implementation. This section covers the inputs required from other workstreams and the outputs expected from each phase. + +## Discovery phase @@ -9 +13 @@ The three primary phases are discovery, design, and implementation. This section -Discovery is the first phase. It forms the basis of operations readiness. During discovery, you should: +Discovery is the first phase. It forms the basis of operations readiness. During discovery, you should: @@ -11 +15 @@ Discovery is the first phase. It forms the basis of operations readiness. During - * Hold workshop or kickoff meetings to come up with a prioritized list of operational domains that need to be modernized. + * Hold workshop or kickoff meetings to come up with a prioritized list of operational domains that need to be modernized. @@ -15 +19 @@ Discovery is the first phase. It forms the basis of operations readiness. During - * Review documentation, such as playbooks, runbooks, and organizational charts. + * Review documentation such as playbooks, runbooks, and organizational charts. @@ -20,0 +25,35 @@ Discovery is the first phase. It forms the basis of operations readiness. During + * Assess your current tooling and technology stack. + + * Evaluate skill gaps and training needs. + + + + +## Design phase + +The design phase usually begins soon after discovery and before implementation. However, depending on your delivery methodology (for example, if you're using an agile approach), design and implementation can occur in the same sprint. During the design phase, you use insights from the discovery phase to address gaps and to refine, improve, or even eliminate existing processes and procedures. Key activities include: + + * Creating specific deliverables (for example, architecture diagrams and process flows) + + * Planning change management activities + + * Determining risk assessment and mitigation strategies + + * Planning the timeline and resource allocation + + + + +## Implementation phase + +Implementation can begin in parallel with the design phase depending on your delivery methodology (for example, agile). During the implementation phase, focus shifts to executing the designed solutions and preparing the organization for adoption. Key activities include: + + * Developing a phased rollout strategy + + * Defining training and documentation requirements + + * Establishing success metrics and key performance Indicators (KPIs) + + * Defining a post-implementation review process + + * Testing for operational readiness @@ -24 +62,0 @@ Discovery is the first phase. It forms the basis of operations readiness. During -The design phase usually begins soon after discovery and before implementation, but you can perform design and implementation in the same sprint. During the design phase, you use the information you gathered during discovery to address gaps and change, improve, or even eliminate processes and procedures. @@ -26 +64 @@ The design phase usually begins soon after discovery and before implementation, -Because the design and implementation phases form the basis of operational automation and integration, everything must be in place and production-ready before the go-live date. For information about what to account for during the design and implementation phases, see the [Best practices and recommendations](./best-practices.html) section. +The design and implementation phases are critical to operational automation and integration. For this reason, everything must be fully prepared and production-ready before the go-live date. For detailed guidance on what to consider during these phases, see the [Best practices and recommendations](./best-practices.html) section. @@ -28 +66 @@ Because the design and implementation phases form the basis of operational autom -Perform these phases in a logical manner in one or more sprints. Deliver core operations functions or other prioritized domains. You can capture the work for each phase in a cloud playbook. A playbook can take the form of scripts, automated runbooks, or even a summary of processes or steps required to operate your modernized environment. +Perform these phases in a logical manner in one or more sprints. Deliver functions for core operations or other prioritized domains. You can capture the work for each phase in a cloud playbook. A playbook can take the form of scripts, automated runbooks, or even a summary of processes or steps required to operate your modernized environment. @@ -30 +68 @@ Perform these phases in a logical manner in one or more sprints. Deliver core op -The following diagram shows the 15 OI domains organized in 4 functions: core operations, security and control, business management, and supporting functions. +The following diagram shows the 21 OI domains organized in 4 functions: core operations, security and control, business management, and supporting functions. These are described in detail in the [next section](./best-practices.html). @@ -32 +70 @@ The following diagram shows the 15 OI domains organized in 4 functions: core ope - +