update 7 files and delete 2 files

105-Well Architected/wds/00-Workshop Introduction/01_workshop_intro.md

@@ -54,3 +54,5 @@ This workshop is primarily focused on phases one, two, and three, in which you:
 * 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.
+
+**Total Duration**: 90 minutes

105-Well Architected/wds/00-Workshop Introduction/readme.md

@@ -8,7 +8,7 @@
 
 ## Workshop Introduction
 
-At the end of the workshop, participants will be able to:
+At the end of this 2-day 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.

105-Well Architected/wds/01-Understanding customers business and technical needs/01_determine_customer_objectives.md

@@ -33,7 +33,7 @@ In this activity, you'll use the information provided in the customer scenario t
   * What is the business priority?
 * Document your answers.
 
-**Duration**: 40 minutes
+**Duration**: 90 minutes
 
 ### Participant steps
 

105-Well Architected/wds/01-Understanding customers business and technical needs/readme.md

@@ -16,4 +16,4 @@ At the end of the unit, participants will be able to:
 **Overview**
 In this unit, you will read the customer scenario to understand their needs and objectives. Select either the platform as a service scenario or the infrastructure as a service scenario, depending on what is most relevant to your group.
 
-**Total Duration**: 40 minutes
+**Total Duration**: 90 minutes

105-Well Architected/wds/02-AWAF Cross Functional Areas/01_awaf_cross_functional_areas_analysis.md

@@ -77,7 +77,7 @@ The first step in this whiteboard will be to discuss resiliency. To do this, wal
    * How does the architecture align to a BCDR strategy that meets those requirements?
    * Does the architecture allow for automated and routine testing of the BCDR strategy?
 
-**Duration**: 20 minutes
+**Duration**: 30 minutes
 
 **Participant steps**
 
@@ -135,7 +135,7 @@ Working with your team, brainstorm solutions related to performance and scale wi
    * What are the key scaling points within the architecture?
    * What are the scaling requirements for these points (auto or reactive, proactive)?
 
-**Duration**: 20 minutes
+**Duration**: 30 minutes
 
 **Participant steps**
 
@@ -190,7 +190,7 @@ Working with your team, brainstorm solutions related to security, governance, an
    * What are the functional and nonfunctional requirements for identity (internal and external) relative to the workload, and how does the architecture align with those requirements?
    * What governance policies are in place that would affect the design and security of the workload architecture?
 
-**Duration**: 20 minutes
+**Duration**: 30 minutes
 
 **Participant Steps**
 
@@ -242,7 +242,7 @@ Working with your team, brainstorm solutions related to DevOps within a Well-Arc
    * Do these pipelines include automated tests, code scanning, and/or security scanning?
    * Are there any approval gates within the pipelines?
 
-**Duration**: 20 minutes
+**Duration**: 30 minutes
 
 **Participant steps**
 
@@ -298,7 +298,7 @@ Working with your team, brainstorm solutions related to observability within a W
    * What tools will be leveraged for capturing, monitoring, and alerting on the telemetry?
    * Are there any external dependencies that require access to this telemetry?
 
-**Duration**: 20 minutes
+**Duration**: 30 minutes
 
 **Participant steps**
 

105-Well Architected/wds/02-AWAF Cross Functional Areas/readme.md

@@ -22,4 +22,4 @@ The goal of this session is to ensure that the solutions your team develops are
 
 After completing the whiteboard, you'll also complete a discussion activity to help you identify key themes and important takeaways from your whiteboard session before moving on to the prioritization phase of today's workshop.
 
-**Total Duration**: 2.5hours
+**Total Duration**: 3hours

105-Well Architected/wds/03-Developing a prioritized list of recommendations/01_assessing_priorities.md

@@ -21,7 +21,7 @@ Team lead guidance
 
 Participants will engage in a team exercise to refine their list of potential solutions by prioritizing for impact and alignment with the customer's business objectives. They will also complete an observation chart summarizing their recommendations to prepare for the customer presentation.
 
-**Duration**: 45minutes
+**Duration**: 90minutes
 
 **Participant guidance**
 
@@ -61,3 +61,5 @@ Keep in mind that some goals will have to be met in phases and that certain solu
 **Summary**
 
 In this exercise, participants refined their ideas, identifying the most urgent and actionable solutions, while also considering the long-term plan for the customer's architecture.
+
+In the next exercise you will prepare for your customer conversation by first translating your recommendations into one or more solution architecture diagrams.

105-Well Architected/wds/03-Developing a prioritized list of recommendations/README.md

@@ -18,4 +18,4 @@ By the end of this unit, you will be able to:
 
 In this unit, you'll refine your brainstorming results into an observation chart that serves as a priority matrix for establishing a Well-Architected PaaS or IaaS Framework for the customer.
 
-**Total Duration**: 1hour
+**Total Duration**: 90minutes

105-Well Architected/wds/04-AWAF Solution Presentation/01_solution_architecture.md

@@ -0,0 +1,55 @@
+# Architecting for Success
+
+---
+
+## 105 - Azure Well Architected Workshop
+
+---
+
+## Customer Solution Architecture Presentation
+
+**Objective**
+By the end of this exercise, you will be able to:
+* Practice proactive customer conversations around the Well-Architected Framework.
+
+**Team lead guidance**
+
+* Explain that team members will now practice presenting the recommendations developed by the team in the previous activity.
+* All team members must participate in the team presentation and should work together to assign roles and responsibilities and provide each other with feedback during the practice session.  
+* Set the time for when the team members need to conclude the discussion.
+* Instruct the team to each choose one of the cross-functional areas to present. Some people may need to present more than one area if you do not have at least five people on your team.
+
+**Overview**
+
+Your team will now practice as if you were delivering a pitch to the customer. The findings and recommendations for each cross-functional area should be presented by one of the team members. One person should also take on the role of wrapping up and summarizing the recommendations in a holistic way.
+
+**Duration:** 1hr 15minutes
+
+**Participant guidance**
+
+Being a Solutions Architect means being responsible for the design and implementation of technical solutions that meet the requirements of a business goal or project. Your solution should be based on the customer's needs and priorities. You should also consider the customer's budget and timeline.
+
+Use the **observation chart** with all the required notes that were created during the workshop to design one more solution architectures.
+Use a **storytelling strategy** to present the solution to your customer. Remember that in real life, the customer might not understand technical vocabulary. Clients may not know how a technical solution looks or how it should be presented.
+Identify the **architecture style**: The first step is to identify the architecture style that suits your requirements. It could be a microservices architecture, a more traditional N-tier application, or a big data solution.
+Choose the **main technology pieces**: Once you have identified the architecture style, you can start choosing the main technology pieces for the architecture. For example, if you are building a microservices architecture, you might choose to use Azure Kubernetes Service (AKS) for hosting the microservices, Azure Cosmos DB for the database, and Azure Active Directory (Azure AD) for authentication and authorization.
+Design for **scalability and resilience**: Applications should be designed to scale horizontally, adding new instances as demand requires. They should also be resilient when failures occur. For example, if a microservice fails, the application should be able to continue to function without that microservice.
+**Automate deployments**: Deployments must be automated and predictable. This is especially important for cloud applications, where you might need to deploy to multiple environments, such as development, test, and production.
+**Monitor and gain insights**: Monitoring and telemetry are critical for gaining insight into the system. You should be able to monitor the health of the system and individual components, and you should be able to gain insights into how the system is being used.
+**Refer to Azure Architecture Center**: Microsoft provides an Azure Architecture Center that offers architecture diagrams and technology descriptions for reference architectures, real-world examples of cloud architectures, and solution ideas for common workloads on Azure ³. The center also provides a guide for Azure Application Architecture that covers architecture styles for cloud applications, technology choices, design principles, the five pillars of software quality, and cloud design patterns.
+
+**Participant steps**
+
+1. Choose your desired topic and take a couple of minutes to prepare your presentation.
+2. All team members will take turns presenting their topics. Plan to speak for about two to three minutes.
+3. Listen to your teammates' presentations.
+4. Provide each other with constructive feedback and coaching.
+
+**Tips**
+
+The solution designs can be high-level design diagrams. Functional requirements are not in scope of this exercise, but non-functional requirements should be considered and documented.
+
+**Activity summary**
+
+Now that you created one or more solution designs, it is time to put everything into a presentation and practice your presentation with your team.
+

105-Well Architected/wds/04-AWAF Solution Presentation/01_practicing_the_customer_presentation.md → 105-Well Architected/wds/04-AWAF Solution Presentation/02_practicing_the_customer_presentation.md

@@ -23,7 +23,7 @@ By the end of this exercise, you will be able to:
 
 Your team will now practice as if you were delivering a pitch to the customer. The findings and recommendations for each cross-functional area should be presented by one of the team members. One person should also take on the role of wrapping up and summarizing the recommendations in a holistic way.
 
-**Duration:** 30 minutes
+**Duration:** 1hr 15min
 
 **Participant guidance**
 

105-Well Architected/wds/04-AWAF Solution Presentation/02_presenting_to_the_customer.md → 105-Well Architected/wds/04-AWAF Solution Presentation/03_presenting_to_the_customer.md

@@ -21,7 +21,7 @@ Be prepared to facilitate the activity as needed and assign a speaking order to
 
 All team members must participate in the team presentation and should work together to assign roles and responsibilities and provide each other with feedback during the practice session.
 
-**Duration**: 15 minutes per team
+**Duration**: 20minutes per team
 
 **Participant guidance**
 
@@ -32,10 +32,10 @@ The coach will act as a customer.
 **Participant steps**
 
 1. Go back to the Team channel and verify that all team members are present.
-2. Time is limited. Assign an observer who will keep track of the customer conversations and feedback sessions and ensure that all teams stay within the timeframes (ten minutes for each conversation presentation and five minutes for feedback).
+2. Time is limited. Assign an observer who will keep track of the customer conversations and feedback sessions and ensure that all teams stay within the timeframes (20 minutes for each conversation presentation and five minutes for feedback).
 3. Deliver customer conversations (in pairs) to the team.
-   * [Pair 1: 10-minute customer conversation. Pairs 2, 3, and 4: listen + 5-minute feedback.]  
-   * [Pair 2: 10-minute customer conversation. Pairs 1, 3 and 4: listen + 5-minute feedback.]  
+   * [Pair 1: 20-minute customer conversation. Pairs 2, 3, and 4: listen + 5-minute feedback.]  
+   * [Pair 2: 20-minute customer conversation. Pairs 1, 3 and 4: listen + 5-minute feedback.]  
    * [Pair 3: 10-minute customer conversation. Pairs 1, 2 and 4: listen + 5-minute feedback.]  
    * [Pair 4: 10-minute customer conversation. Pairs 1, 2 and 3: listen + 5-minute feedback.]
 4. Team members should provide feedback to each participant and should include:

105-Well Architected/wds/04-AWAF Solution Presentation/readme.md

@@ -17,4 +17,4 @@ By the end of this unit, you will be able to:
 
 In this unit, you will present a proposed solution, modeling a real customer conversation. Based on feedback, you will also identify strengths and areas for improvement in your proposed solution.
 
-**Total Duration**: 1hour
+**Total Duration**: 3hours