sep 2023 content update

jonathan-vella · Sep 20, 2023 · d5deb3e · d5deb3e
1 parent 7de3ecd
commit d5deb3e
Show file tree

Hide file tree

Showing 14 changed files with 156 additions and 1 deletion.
diff --git a/...ds/00_workshop_intro/01_workshop_intro.md → ...orkshop Introduction/01_workshop_intro.md b/...ds/00_workshop_intro/01_workshop_intro.md → ...orkshop Introduction/01_workshop_intro.md
diff --git a/...chitected/wds/00_workshop_intro/readme.md → ...ed/wds/00-Workshop Introduction/readme.md b/...chitected/wds/00_workshop_intro/readme.md → ...ed/wds/00-Workshop Introduction/readme.md
diff --git a/...ation/01_determine_customer_objectives.md → ...needs/01_determine_customer_objectives.md b/...ation/01_determine_customer_objectives.md → ...needs/01_determine_customer_objectives.md
diff --git a/...onversation/02a_customer_scenario_paas.md → ...nical needs/02a_customer_scenario_paas.md b/...onversation/02a_customer_scenario_paas.md → ...nical needs/02a_customer_scenario_paas.md
diff --git a/...onversation/02b_customer_scenario_iaas.md → ...nical needs/02b_customer_scenario_iaas.md b/...onversation/02b_customer_scenario_iaas.md → ...nical needs/02b_customer_scenario_iaas.md
diff --git a/...our_customer_conversation/adatum_paas.png → ...iness and technical needs/adatum_paas.png b/...our_customer_conversation/adatum_paas.png → ...iness and technical needs/adatum_paas.png
diff --git a/...our_customer_conversation/costal_iaas.png → ...iness and technical needs/costal_iaas.png b/...our_customer_conversation/costal_iaas.png → ...iness and technical needs/costal_iaas.png
diff --git a/..._for_your_customer_conversation/readme.md → ...rs business and technical needs/readme.md b/..._for_your_customer_conversation/readme.md → ...rs business and technical needs/readme.md
diff --git a/...1_awaf_cross_functional areas analysis.md → ...1_awaf_cross_functional_areas_analysis.md b/...1_awaf_cross_functional areas analysis.md → ...1_awaf_cross_functional_areas_analysis.md
@@ -25,7 +25,7 @@ In this phase, **get all your ideas down on paper**. Once you've completed the w
 
 **Team lead guidance**
 
-* This whiteboard will be completed collaboratively using the provided table.
+* This whiteboard will be completed collaboratively using the [provided table](./02_whiteboard_table.md).
 * Encourage all members to brainstorm and share their ideas on how to make the current architecture more resilient.
 * You may choose to start the discussion by level-setting with your team on the basics of resiliency by reviewing the provided resources.
 * Assign a timekeeper so your team gets through all of the topics before the end of the session.

diff --git a/...chitected/wds/02-Well Architected Cross Functional Areas/02_whiteboard_table.md b/...chitected/wds/02-Well Architected Cross Functional Areas/02_whiteboard_table.md
@@ -0,0 +1,17 @@
+# Architecting for Success
+
+---
+
+## 106 - Microsoft Azure Well Architected Workshop
+
+---
+
+## Whiteboard table for AWAF cross-functional areas analysis
+
+Resiliency | Performance and Scale | Security, Governance, and Identity  | DevOps  | Observability 
+-----------|-----------------------|-------------------------------------|---------|---------------
+  | - | - | - | - | -
+  | - | - | - | - | -
+  | - | - | - | - | -
+  | - | - | - | - | -
+  | - | - | - | - | -
diff --git a/...hitected Cross Functional Areas/03_awaf_cross_functional_strategy_assessment.md b/...hitected Cross Functional Areas/03_awaf_cross_functional_strategy_assessment.md
@@ -0,0 +1,40 @@
+# Architecting for Success
+
+---
+
+## 106 - Microsoft Azure Well Architected Workshop
+
+---
+
+## Analyze the Well-Architected Framework's cross-functional strategy
+
+**Activity overview**
+
+Participants will synthesize the results of the whiteboard session to analyze the Well-Architected Framework's cross-functional strategy.
+
+**Objective**
+By the end of this unit, you will be able to:
+
+* Outline customer needs, business priorities, and key architectural characteristics given a realistic customer workload.
+* Conduct a cross-pillar analysis and determine key gaps in the workload's alignment with the Well-Architected Framework.
+
+Duration: 15 minutes
+
+**Participant guidance**
+
+Considering the customer scenario and the takeaways of the whiteboarding session, discuss the following questions with your team:
+* What key themes and observations emerged in your whiteboarding session?
+* Can you identify any particular challenge areas where customer priorities might require tradeoffs or come into conflict with one another?
+* How can these be addressed?
+* Do your recommendations account for a strategic and long-term viability perspective?
+* Have you assessed the customer's workload from a holistic five-pillars perspective?
+
+**Participant steps**
+
+1. Use your observation chart to help you answer the questions.
+2. Document your answers.
+3. Go to the next activity to begin the prioritization phase of this workshop.
+
+**Summary**
+
+This activity helped participants synthesize insights from their whiteboarding session before moving on to the prioritization phase of the Well-Architected Framework.
diff --git a/...stomer_recommendations_analysis/readme.md → ...hitected Cross Functional Areas/readme.md b/...stomer_recommendations_analysis/readme.md → ...hitected Cross Functional Areas/readme.md
diff --git a/...l Architected/wds/03-Developing a prioritized list of recommendations/README.md b/...l Architected/wds/03-Developing a prioritized list of recommendations/README.md
@@ -0,0 +1,49 @@
+# Architecting for Success
+
+---
+
+## 106 - Azure Well Architected Workshop
+
+### Workshop Introduction
+
+The Well-Architected Framework (WAF) mindset focuses on overall workload health, highlighting the full picture of the customer's architecture, and the importance of an iterative, five-pillar approach. Working within a Well-Architected Framework requires a shift away from narrow, siloed solutions and toward holistic, integrative approaches to solving a customer's infrastructure as a service (IaaS) challenges. At the end of the workshop, participants will be able to:
+
+* Outline customer needs, business priorities, and key architectural characteristics given a realistic customer workload.
+* Conduct a cross-pillar analysis and determine key gaps in the workload's alignment with the Well-Architected Framework.
+* Develop a prioritized list of recommendations and next steps.
+* Practice proactive customer conversations around the Well-Architected Framework.
+
+---
+
+### Basics of the Well-Architected Framework
+
+Employing a Well-Architected Framework begins with understanding the five-pillar approach, which acknowledges that any high-functioning framework addresses the following areas:
+
+* Reliability - The ability of a system to recover from failures and continue to function.
+* Security - Protecting applications and data from threats.
+* Cost optimization - Managing costs to maximize the value delivered.
+* Operational excellence - Operations processes that keep a system running in production.
+* Performance efficiency - The ability of a system to adapt to changes in load.
+
+The strategic and long-term viability of the workload requires an end-to-end, holistic review spanning all five pillars.
+
+---
+
+### Cross-functional areas
+
+Our customers do not think of their needs and goals in terms of pillars. Rather, they seek to accomplish cross-functional goals to meet their business objectives. In this workshop, we'll review a customer scenario and identify solutions for five common cross-functional areas of focus:
+
+* Resiliency - Analyze how business continuity and disaster recovery requirements are being addressed by the workload architecture and operational strategies.
+* Performance and Scale - Analyze the performance and scalability requirements within the workload architecture; evaluate how they contribute to and/or are affected by the overall fault tolerance of the workload.
+* Security, Governance & Identity - Analyze how security, governance, and identity requirements are being addressed by the workload architecture and operational strategies.
+* DevOps - Analyze the automation and deployment strategies for the workload.
+* Observability - Analyze how observability requirements are being addressed by the workload architecture and operational strategies.
+
+---
+
+### An iterative approach 
+It's also important to recognize that implementing a Well-Architected Framework requires an iterative approach, as described in the workflow diagram.
+
+> ![Well-Architected Framework workflow](/106-Well%20Architected/images/waf_workflow.png)
+
+This workshop is primarily focused on phases one, two, and three, in which you Discover the customer's needs, Analyze to identify potential solutions, and Prioritize—or conduct triage to determine what needs to be implemented first. We will also discuss the optimization that occurs post-implementation to further enhance and refine the customer's architecture.
diff --git a/106-Well Architected/wds/05-AWAF remediation and optimization/README.md b/106-Well Architected/wds/05-AWAF remediation and optimization/README.md
@@ -0,0 +1,49 @@
+# Architecting for Success
+
+---
+
+## 106 - Azure Well Architected Workshop
+
+### Workshop Introduction
+
+The Well-Architected Framework (WAF) mindset focuses on overall workload health, highlighting the full picture of the customer's architecture, and the importance of an iterative, five-pillar approach. Working within a Well-Architected Framework requires a shift away from narrow, siloed solutions and toward holistic, integrative approaches to solving a customer's infrastructure as a service (IaaS) challenges. At the end of the workshop, participants will be able to:
+
+* Outline customer needs, business priorities, and key architectural characteristics given a realistic customer workload.
+* Conduct a cross-pillar analysis and determine key gaps in the workload's alignment with the Well-Architected Framework.
+* Develop a prioritized list of recommendations and next steps.
+* Practice proactive customer conversations around the Well-Architected Framework.
+
+---
+
+### Basics of the Well-Architected Framework
+
+Employing a Well-Architected Framework begins with understanding the five-pillar approach, which acknowledges that any high-functioning framework addresses the following areas:
+
+* Reliability - The ability of a system to recover from failures and continue to function.
+* Security - Protecting applications and data from threats.
+* Cost optimization - Managing costs to maximize the value delivered.
+* Operational excellence - Operations processes that keep a system running in production.
+* Performance efficiency - The ability of a system to adapt to changes in load.
+
+The strategic and long-term viability of the workload requires an end-to-end, holistic review spanning all five pillars.
+
+---
+
+### Cross-functional areas
+
+Our customers do not think of their needs and goals in terms of pillars. Rather, they seek to accomplish cross-functional goals to meet their business objectives. In this workshop, we'll review a customer scenario and identify solutions for five common cross-functional areas of focus:
+
+* Resiliency - Analyze how business continuity and disaster recovery requirements are being addressed by the workload architecture and operational strategies.
+* Performance and Scale - Analyze the performance and scalability requirements within the workload architecture; evaluate how they contribute to and/or are affected by the overall fault tolerance of the workload.
+* Security, Governance & Identity - Analyze how security, governance, and identity requirements are being addressed by the workload architecture and operational strategies.
+* DevOps - Analyze the automation and deployment strategies for the workload.
+* Observability - Analyze how observability requirements are being addressed by the workload architecture and operational strategies.
+
+---
+
+### An iterative approach 
+It's also important to recognize that implementing a Well-Architected Framework requires an iterative approach, as described in the workflow diagram.
+
+> ![Well-Architected Framework workflow](/106-Well%20Architected/images/waf_workflow.png)
+
+This workshop is primarily focused on phases one, two, and three, in which you Discover the customer's needs, Analyze to identify potential solutions, and Prioritize—or conduct triage to determine what needs to be implemented first. We will also discuss the optimization that occurs post-implementation to further enhance and refine the customer's architecture.