1. Slide 1: pause on the title, then reveal the line.
   For the next two days you are not students. You are founders. You're going to build a company in the cloud, and tomorrow we find out if it survives.
2. Slide 2: walk through today’s agenda and breaks; show when LinkedIn and GitHub icebreakers happen.
3. Slide 3: use the three-site illustration: Workshop site for instructions, ChaiCart Live for student work and credits, and the Azure demo for simulated orders and incidents. Introduce Build → Survive → Pitch and the 1,000 starting credits.
4. Slide 4: explain teams as availability zones and regions. Introduce the four captains by name and region; ask each region to cheer.
5. Slide 5: start the 5-minute timer. Students sign in with Google, join using their team code and assign the five roles. Explain the illustrated handoff: COO submits team work, captain reviews and can apply the award to the ledger; the facilitator can apply it too. Cloud or Not uses individual answers at +100 each; recap quizzes use the COO’s answer at +10. Reveal and Score applies automatic points.
6. Slide 6: LinkedIn icebreaker (7 min). Pair students across teams, scan the presenter’s QR, and make a useful introduction. Captains approve +100 reviews after all five members complete; the captain or facilitator applies each review once; existing profiles and connections count.
7. Slide 7: everyone stands. Reveal items one by one: stand = cloud, sit = not cloud. Hand the mic to one student per item to justify.
8. Slide 8: Use Reveal and score for each Cloud-or-Not question; award +100 per correct participant and add those credits to their teams. Check individual work under Students; discuss UPI and Excel as the two twists.

• “What makes something cloud?” Look for: someone else runs it, network access, shared, pay for what you use.

1. Slide 9: electricity analogy; reveal the five cards. For each, ask a random table: “What's the ChaiCart example?”
2. Slide 10: Teams arrange the 12 digital event cards. No talking for the first two minutes; then discuss and submit. The app locks only a correct order. Captain checks server timestamps and approves the first correct team in each region; captain or facilitator applies +50 once; incorrect orders can be reviewed with zero-credit feedback.
3. Slide 11: reveal the timeline year by year while teams check their line. Then the three eras.
   We went from sharing one big computer, to everyone owning their own, and now back to sharing. Only this time the sharing is global and on demand.
4. Slide 12: reveal the six drivers. Ask one team per region which driver matters most to ChaiCart.

1. Slide 14: Biryani-as-a-Service. Ask: “Who has ordered on Swiggy? Why not cook?” The answer is always control vs effort.
2. Slide 15: map the analogy to the stack, one row at a time: “In PaaS, who patches the OS? The provider. That's why developers love it.”
3. Slide 16: sorting race, 6-minute timer. Run → Service Model Sort → Launch on phones; teams classify the digital cards, and COO submits.
4. Slide 17: reveal column by column. Captains compare the stored classification with the protected key; the review computes five points per correct card. Captain or facilitator applies the reviewed score once. Discuss the tricky ones: Azure Functions (serverless, PaaS family), Blob Storage (raw infrastructure), Dynatrace (SaaS).

• “ChaiCart has 3 developers and no ops person. Which model for the app? For email? For the database?”

1. Slide 19: hotel, own house, house + Airbnb, many hotel chains.
2. Slide 20: captains assign one digital scenario per table, so three teams share each scenario. 3-minute timer to decide.
3. Go through the eight scenarios. For each, ask the three teams to raise hands, pick one at random for a 60-second defence (handheld mic), then let one of the other two challenge with a single question.
4. Best debates: bank (regulation vs innovation), hospital (sensitive data + AI), factory (latency → edge).
5. Slide 21: debrief the six factors. Mention RBI data localisation and the DPDP Act as real Indian constraints.

1. Slides 23–24: the landscape and the “Rosetta Stone”. Quiz the room by pointing at a row and asking for the Azure name.
2. Slide 25: teams open their assigned provider card and the client brief above the Shark Tank pitch form. 8 minutes to prepare.
3. Region round (10 min): in each quadrant, every CEO pitches for 1 minute while the captain times. Each team then votes for the best pitch, not its own. The captain announces the region winner.
4. Grand final (15 min): the four region winners pitch for 2 minutes on stage. You ask each the “They will ask” question from their card. You and the captains pick the grand winner.

1. Slide 26: GitHub networking (7 min). Improve profiles, follow peers and the presenter, and discuss one shared project idea. Captains approve +100 reviews after all five members complete; the captain or facilitator applies each review once; finish delayed signups during a break.
2. Slide 27, Bingo (8 min): read clues from the Workshop clue caller in random order, ticking each one. The COO submits a Bingo claim; captains check its digital line against called terms. Confirm the first three valid room-wide claims before applying credits.
3. Slide 29: house → apartment → tiffin box. “In an apartment, what's shared and what's yours? In a tiffin service?” (The kitchen = the kernel.)
4. Slide 30: walk both stacks from bottom to top; reveal the Kubernetes line.
5. Slide 31, live demo: start a VM in the portal (in rg-chaicart-day1), then immediately run the container commands in Cloud Shell. The room bets on which serves a page first. Open the container's IP on screen.
6. After the session: az group delete -n rg-chaicart-day1 --yes.

1. Slides 33–34: the building blocks, then trace one request from phone to database. Reveal the three principles.
2. Slide 35: 15-minute build. Teams build and save their architecture in ChaiCart Live. Captains circulate asking: “What happens if this box dies?”
3. At 15 minutes, reveal the Diwali twist and start the 7-minute timer.
4. Region judging (8 min): captains walk their six tables with the six Well-Architected questions from slide 36 and pick the region's best design.
5. Main stage (8 min): the four region winners show their saved app design and explain it in 90 seconds each. Pick the overall best.
   Your facilitator freezes the approved app design. Tomorrow some game cards will ask whether your design had autoscaling, multiple zones or a firewall. Your CTO will have to prove it.

1. Slide 38: one super-chef vs a station kitchen; reveal the cloud-native definition.
2. Invite six volunteers from six different teams (at least one per region) to the stage. Everyone else counts out loud.
3. Round 1, monolith (3 min): one volunteer does all five steps on each ticket. Count completed tickets.
4. Round 2, microservices (3 min): five volunteers, one station each. Tickets flow down the line; each assigned volunteer confirms a handoff, which stores the server timestamp.
5. Round 3, chaos (3 min): tap the Payment volunteer; they freeze. After 30 seconds, ask the room: “Where is order CC-007 right now?” Let the volunteers read the timestamps aloud.
6. Slide 40: reveal the three insights; land the last card: the ticket was a distributed trace. If time allows, place an order in the deployed app and expand its trace in the facilitator console: cart → payment → pool → demo database → gateway → business events. These are logical services in one Node process, not independently deployed microservices.

1. Assign two teams to each station (a region's six teams start at six neighbouring stations). Every 3 minutes, all teams move clockwise to the next station.
2. Six rotations cover all six case studies. Each team adds digital reflections: Which cloud concept saved them? and What would ChaiCart copy?
3. While teams walk, captains read notes and flag the best ones. Read out four and award them.
4. Link the Capital One poster (breach and shared responsibility) to Day 2's security topic.

1. Slide 44: the doctor analogy; then the monitoring vs observability quote.
2. Slide 45, 5-minute Dynatrace peek: service map, a response-time chart, your story trace (“this is the order ticket from the kitchen!”), the Problems page. Ask the audience question on the slide.
3. Slide 46, quiz: Open the Day 1 quiz from Run. COO submits one team answer per question; lock before advancing and use the quiz panel to score +10 per correct.
4. Slide 47: Preview the incident teaser; evidence unlocks in the app on Day 2.
5. Show the Day 1 leaderboard in presentation mode.

• Freeze approved architecture designs for all 24 teams in Workshop.
• Delete rg-chaicart-day1. Export the leaderboard CSV as a backup.
• Check digital incident evidence and keep its solution protected.

1. Slide 1: use the build–test–recover illustration to connect yesterday’s design to today’s incident work. The loop is observe → explain → restore → learn. The Azure demo simulates dependencies; student designs do not provision cloud resources.
2. Slide 2: walk through the Day 2 agenda, breaks and final Demo Day.
3. Slide 3: one team per region shouts one word for Day 1. Show the leaderboard; remind everyone of the five roles.
4. Slide 4: X learning circle (5 min kickoff, continuing throughout Day 2). Students improve their bio and find peers, then share workshop photos or takeaways with #ChaiCartCloudWorkshop. Show the hashtag search and announce the Best Workshop Post or Photo award. Collect best-post links through captains before the final awards; judge learning value, creativity and workshop spirit, not likes. Ask permission before sharing someone’s photo; no public post is required. Captains approve +100 reviews after all five members complete; the captain or facilitator applies each review once; posting is optional.
5. Slide 5: read the breaking news dramatically; reveal the “payment stuck on spinner” line and pause.

1. Slide 7: the four user-facing signals. Explain p95 with the “95 happy, 5 tweeting” example.
2. Slide 8: Open Guess the Downtime; COO submits four annual-minute guesses. Captains compare the closest team per row.
3. Ask: “Does a chai app need five nines? Does UPI?”
4. Slide 9: the six reliability patterns, linked back to the Human Kitchen.

1. Slide 11: smoke alarm vs fire investigator; reveal APM.
2. Slide 12: the golden signals, RED and USE. Stress the final hint about connection pools. It is a deliberate clue for the mystery.

1. Slide 13: Open the digital mystery evidence from Run. Captains inspect stored timestamped accusations.
2. Slide 14: introduce the six suspects with some theatre.
3. Slide 15: rules and scoring. 25-minute timer. COOs submit one final accusation in Live; the app records the server timestamp and locks it. No paper forms or handwritten times are needed.
4. Hints (announce to the whole room if most teams are stuck):
   • At 10 min: “Compare database connections before and after 08:58.”
   • At 15 min: “Look at the log lines from two days ago, then today's.”
   • At 20 min: “In the failed trace, what's missing?”
5. While teams work, captains review the evidence and proposed fixes. In the facilitator mystery panel, tick good fix/prevention submissions before applying. The grader uses server timestamps to add the +100 first-correct killer-and-weapon bonus; do not award that bonus again manually. Lock, reveal the solution on the slides, then press Apply mystery credits once.
6. Slide 16, reveal: go suspect by suspect, innocents first. Ask the room to shout “innocent” or “guilty” before each reveal.
7. Slide 17, lessons: stress the irony: a cost-saving change caused the outage. After the reveal, use the deployed app companion if rehearsed: baseline in Healthy / Roll back, select Deploy Dave: pool 50 → 5, launch the surge, compare waits/504s and missing gateway spans, then roll back and stop traffic. Keep controls hidden during the incident investigation. Live timings differ from prepared evidence.

Deploy Dave (payment-service v2.3.1 at 08:58) cut the DB connection pool from 50 to 5 to save cost. Traffic Tara (3× launch traffic at 09:00) exhausted the five connections. Requests waited 30 s and timed out, and checkout returned 504s. The database, gateway, cache and disk are innocent: the database was starved, not overloaded.

1. Slides 19–20: the same incident as a metric, a log and a trace; how tracing works (trace ID = ticket number, span = station).
2. Slide 21, Part A, Dynatrace (~20 min): you drive the screen. Read each question, give teams 90 seconds to discuss, then take a suggestion from a random table on where to click. Teams write answers from what they see.
3. Part B, Azure (~15 min): share the deployed ChaiCart QR code. Teams open the menu and sign in with Google to place demo orders. Show the App Service resource and the app console. Request /chai-not-found for a real 404. Show Live Metrics and run the worksheet KQL only after Application Insights ingestion is verified; otherwise use prepared evidence or a separately instrumented app. Confirm the budget alert exists before presenting Q14; budget alerts do not cap spending.
4. Discuss answers; captains review the stored 15 responses and evidence before proposing credits.
5. Slide 22: recap with the DQL examples: observability is asking new questions without shipping new code.

1. Slides 24–25: the Treynor Sloss quote, then SLI → SLO → SLA. Do the error-budget maths live: 30 × 24 × 60 × 0.1% ≈ 43 minutes.
2. Slide 26: each SRE holds the 43-minute budget. Read one card aloud and start the 60-second timer. Teams discuss A/B; the COO submits the shared choice on their phone. Use Issue immutable staff rolls for this card when required, before submission. Next card advances; End the month enables Apply final credits. Apply once; do not collect separate paper choices or dice rolls.
3. Cards 3 and 8 depend on the Day 1 architecture: the CTO must show proof on the frozen app design to the captain. Before Day 2, approve and freeze every completed team design, not only the four winners.
4. Card 10 ends the month. Ask the team deepest in the red what it would do differently.

1. Explain the blame vs blameless examples on the slide; start the 12-minute timer.
2. Captains circulate. If they hear “Dave messed up”, they ask: “What in our system let that change reach production?”
3. Each captain picks the best postmortem in the region. One region winner reads its root cause and action items on stage; choose the overall best.

1. Slide 29: the DevOps loop, CI, CD and IaC. Keep it short; the game makes the point.
2. Slide 30: Open Digital Delivery Factory from Run. Start round 1 in Workshop for three minutes: COO processes six tickets serially. Stop and discuss queues. Start round 2 for three minutes: CEO plans, CTO builds, SRE tests, COO deploys concurrently. Failed tests return to Build. Compare successful deployments, frequency, lead time and correction time. Region winner: successful deployments, then fewer failures, then lower lead time; +50. These classroom metrics are DORA teaching proxies.
3. Slide 31: DORA metrics and deployment strategies; land the Deploy Dave / canary joke.
4. Slide 32, CI/CD demo: use the repository’s existing ChaiCart workflow. Until Azure deployment credentials are configured, demonstrate passing and failing tests on a rehearsal branch/PR and explain that deployment is skipped. Once deployment is enabled and rehearsed, change chaicart-demo/public/index.html, show the successful deploy, and refresh the Azure URL. Use a controlled failing-test change and revert it immediately after the demonstration; do not leave main broken.

1. Slide 34: shared responsibility; callback to the Capital One poster.
2. Slides 35–37: move briskly. Ask one CFO per region which FinOps lever it would pull first.
3. Slide 38: launch Cloud Bill Shock from Run. The app deals three cards per team; the CFO reads the costs and the CTO checks the frozen design. COO selects the preventing control and submits. The app computes design effects and half-refunds for correct controls; Lock, then Apply bill credits once.
4. Ask each captain for the most painful card in the region, and the room: “Who has seen this happen in real life?”

1. Slide 40: “Which of these have you used without knowing it?” (e.g. HCM when applying for an internship).
2. Slide 41: Commerce starts with the order token, reads its line into the mic, confirms the digital handoff. Each system does the same.
3. Twist: “ERP is down for maintenance!” The ERP volunteer sits. What still works (order, loyalty)? What piles up (invoices)? This is why queues and events matter between systems.
4. Slides 42–43: integration, why SaaS wins, the role of cloud in digital business. In the deployed app, select Pause ERP, place an order, show the queued invoice alongside completed CRM/SCM/HCM/BI events, then select Healthy / Roll back to replay. This is simulated event processing; the app does not connect to SAP, Salesforce or other business systems.

1. Slide 45: vote with hands for the trend that will matter most in five years.
2. Slide 46: students browse the digital career cards in My workshop and discuss roles with teammates. Launch My 90-day cloud plan from Run; every student submits their own plan, not a shared COO answer. 10-minute timer.
3. Slide 47: Preview the incident teaser in the deck; evidence unlocks in the app on Day 2.
4. Slide 48, hot seat: reveal one question at a time and take two or three answers each via the handheld mic. Close with open Q&A about working in the industry.

1. Slide 49: Run the Day 2 quiz with the same team submission and scoring workflow; verify the final leaderboard.
2. Slide 50, region round (15 min): in each quadrant, every CEO pitches for 90 seconds using the five points on the slide. The region votes for its finalist.
3. Grand final (15 min): four finalists pitch for 3 minutes on stage (timer on slide). You and the captains choose Most Creative Pitch.
4. Awards (5 min): show the final leaderboard in presentation mode. Announce Richest Startup, the four Region Champions, Sherlock, Best Architecture, Best Postmortem Most Creative Pitch and Best Workshop Post or Photo. Review the captain shortlists and announce one individual X winner.
5. Slide 51: Share the cheat-sheet link, collect individual post-surveys in the app, record awards, verify attendance, mark the workshop complete, then publish permanent results and digital certificates in InspiredLearning.

Never cut: the Human Kitchen chaos round, Architecture Lego, the murder mystery, and Demo Day.