Who does what.
What happens next.

Open Live → Console → Setup. Create or select ONE workshop session; set its date, assign four captain Google emails and display the Join QR on the projector. Session creation generates all 24 team codes.

Sign in with Google, enter session + team code, choose an available role. Each team has CEO, CTO, CFO, SRE and COO.

Registers the student and reserves one unique role. Setup initializes 24 teams with 1,000 credits each; captains see the six team codes for their region.

Sign in at Captain dashboard, share each code only with its team, check five names/roles per team and help with join issues.

Open the Live projector Screen in a separate tab. Verify one student, one captain and the right session before the opening. Do not create a new session on Day 2.

Run → Pre-workshop survey → Launch on phones; set a short timer.

EVERY student submits confidence ratings and expectations from their own phone.

Stores individual responses; Console shows the results and offers CSV export. A local draft is not a confirmed submission.

Help students who are stuck; do not submit a shared team survey.

Lock / End after checking responses. Use the baseline to compare with the post-survey on Day 2.

Present Day 1 agenda and role responsibilities. Workshop → Open networking / X entries. Show the LinkedIn profile QR from the deck.

Each student improves/creates a profile, connects with peers and Vishruth, then marks LinkedIn complete in My workshop. Existing profiles/connections count.

Keeps individual completion declarations available even while another activity is live.

Review network-linkedin for each team. All FIVE registered members must be complete → Approve for facilitator.

Workshop → Captain approvals → Apply once. Award +100 per eligible team, once. Launching a Run activity is not required for networking.

Run → Cloud or Not? → Launch on phones. Show one question at a time.

EVERY student taps Cloud / Not cloud / It depends once for the current question.

Stores individual answers and personal scores; adds earned credits to team totals and displays answer counts. Students cannot replace a submitted answer.

Encourage discussion and help with phones; no judging or point entry.

Lock answers → Reveal and score → discuss → Next question. Each correct participant earns 100; their team receives the sum. Inspect individual answers under Students. End when finished.

Explain the cloud story; Run → Human Timeline → Launch on phones. First two minutes: no talking.

Team drags event cards oldest → newest. COO submits. If the order is wrong, improve and resubmit while open.

Correct submitted order locks; incorrect order remains editable. Saved server timestamps support the race.

Compare correct submissions and server timestamps across your six teams; approve +50 for the FIRST correct team in your region.

Workshop → Apply once for the four winning reviews. Debrief on slides; Lock / End. Do not award every correct team as a race winner.

Teach IaaS / PaaS / SaaS, then Run → Service Model Sort → Launch on phones.

Team classifies each service card. COO submits the shared classification.

Saves the team choices; captain review compares them with protected keys.

Review service-sort. The review computes +5 for each correct card; add feedback and Approve for facilitator.

Reveal the model discussion on the slides, then Workshop → Apply once. Lock / End the round.

After the 11:00–11:15 break: Run → Where Should They Live? → Launch on phones; explain assigned scenarios and timer.

Team chooses a deployment model and reasons; COO submits. Selected CEOs defend for 60 seconds.

Stores one team response with model + explanation.

Listen for compliance, latency, cost and scale arguments. Approve +30 for convincing defences with evidence.

Workshop → Apply once for approved reviews. Discuss that multiple models can be defensible; Lock / End.

Run → Cloud Shark Tank: pitch brief → Launch on phones; give the startup brief and preparation time.

Team chooses its cloud and business case. COO submits the brief; CEO pitches for one minute in the region.

Stores pitch briefs so captains and facilitator can review them later.

Time all six teams equally. Run the regional pitch round and help the team vote.

Move to Shark Tank: region vote, not manual pitch points yet. Four region winners then pitch in the grand final.

Run → Shark Tank: region vote → Launch on phones after all regional pitches.

Discuss together; COO submits one vote for another team in the same region. No self-vote.

Tallies votes per region; tied leaders are visible.

Check the region tally and resolve or explain ties before awards; invite the finalists. Do not also submit a +50 pitch review for a team scored through the vote.

Lock → Award region winners (+50) ONCE. Pick the overall winner on stage; Leaderboard manual adjustment +100 with a reason. Avoid scoring the same regional win via both vote and review.

After 12:25–13:15 lunch: keep Networking open, show the GitHub QR and give a seven-minute peer introduction.

EVERY student creates/improves a GitHub profile, follows peers and theharithsa, discusses a project, then marks GitHub complete.

Stores per-student completion while other activities continue.

Review network-github after all five members complete → Approve for facilitator.

Workshop → Apply once for +100 per team. Continue to Bingo and containers; no separate Run launch for this networking step.

Run → Cloud Bingo → Launch on phones. Workshop → Cloud Bingo caller: read the clue and press its term.

Team marks called terms on its digital board; COO submits a claim when a row, column or diagonal is complete.

Stores claims and called terms; captain review rejects a line made from uncalled terms.

Check the line and claim timing. Tell facilitator which claims arrived first across the room.

Choose the FIRST THREE valid room-wide claims, approve only those for +30 and Apply once. A valid line alone does not guarantee an award.

Explain VMs and containers on the deck, then switch to the deployed Azure storefront. Keep the Live session running in its other tab.

Students may sign in with Google on the DEMO site, choose items and place a simulated order; this login is separate from joining Live.

Azure returns an order receipt and tracking state. Orders do not become Live quiz answers or credits.

Help students distinguish the Demo storefront from the Live workshop page.

Return to the deck and explain why App Service is PaaS. Cloud provisioning is a presenter demo, not something 120 students must deploy.

Run → Architecture Lego: digital design → Launch on phones. Introduce the components, constraints and Diwali traffic twist.

Team builds a design and rationale; CTO leads the technical choices, COO submits the final shared design.

Saves the design; it is still editable until a confirmed freeze. Day 2 Poker and Bill Shock read the frozen copy.

Review each team against the six Well-Architected questions. Approve every completed design (zero points for non-winners is valid); award +50 to region best.

Apply reviewed credits once; award overall +100 in Leaderboard. In Workshop select EACH team → Freeze approved architecture for Day2. Freeze all 24, not only winners; then Lock / End.

After 14:45–15:00 break: Run → Human Kitchen → Launch. Workshop → Station games: select monolith or service stations, assign registered volunteers and Start order ticket.

Assigned volunteers read their station cards and tap I am this station: hand off. Everyone else watches the order move; COO records the team reflection.

Advances only the currently assigned station, stores timestamped handoffs and shows blocked/recovered tickets.

Confirm who actually volunteered and approve +20 per volunteer from each team, within the rubric.

Compare chaos / monolith with the pipeline; Apply once on volunteer reviews. Explain the handoff story, then Lock / End. No paper tickets required.

Run → Gallery Walk → Launch on phones. Direct students to digital case studies and timed rotations/discussion.

Teams browse cases and write a useful case reflection; COO submits their shared note.

Stores digital reflections for review; no wall posters are required.

Read your region’s notes, shortlist useful reasoning and send recommendations to the facilitator.

Select FOUR best notes in the room. Approve +50 for their teams → Apply once; read the notes aloud and End.

Give the concept recap; Run → Day 1 recap quiz → Launch on phones. Use Live Screen for the projected question.

Team discusses each question; ONLY COO taps its one answer. Other roles watch and discuss.

Stores one answer per team per question; reveals correctness only after your reveal.

Coach participation and check missing teams; do not approve quiz credits separately.

Lock answers → Reveal and score. The app adds +10 per correct team automatically, once per question. Next question repeats the flow; End after question 10.

End the current activity, show the Live leaderboard and tomorrow’s agenda; use remaining time for reflection and questions.

CFO checks the credit ledger; students report missing submissions or disputed awards.

Keeps the same session, registrations, designs, submissions and ledger for Day 2.

Resolve missing roster members/reviews and check every team has an approved design.

Apply outstanding reviews; freeze all designs, stop Demo surge and restore Healthy. Do not use the legacy static leaderboard as a second source of truth.

Select the SAME session; verify projector Screen, captain access and frozen designs. Restore Demo Healthy and stop any surge.

Sign back into Live with the same Google account; confirm team, role and Day 1 credits.

Restores membership and persisted scores; no new registration or credit reset.

Check your six teams are present and designs exist. Help with account/session mismatches.

Show Day 2 agenda and announce the optional post/photo award. Leave networking open during the day.

Workshop → Open networking / X entries; show X profile QR and #ChaiCartCloudWorkshop. Introduce Day 2 story on slides.

EVERY student creates/improves an X profile, finds peers, shares a takeaway and marks X complete. Public posts/photos are optional and can continue all day.

Stores completion and best public post links separately; networking stays available beside live activities.

Approve network-x only when all five members complete. Shortlist optional post/photo links from your region.

Apply once for +100 team credits. Keep the individual Best Workshop Post or Photo award separate; judge learning/creativity, not likes.

Run → Guess the Downtime → Launch; ask for annual downtime in MINUTES for the four availability targets.

Team estimates each row; COO submits the four numbers.

Stores estimates; it does not automatically choose nearest guesses for this form.

Compare each row against the annual-minute answer; closest per region earns +20. Share an award across ties; propose a summed team review, max +80.

Reveal the maths on slides; Workshop → Apply once for approved downtime reviews. Lock / End.

Explain monitoring vs investigation, APM and the golden signals from the deck; keep it concise.

Discuss signals and respond verbally to questions.

No Live activity is required for this teaching block.

Listen for gaps in understanding and help the discussion.

Transition to the mystery; do not open answers or Demo outage controls on the projector ahead of the investigation.

Run → Who Killed Checkout? → Launch; set a 25-minute investigation timer. Reveal hint 1 / 2 / 3 only as needed.

Team reads digital evidence; COO submits ONE final accusation with cause, evidence, fix and prevention.

Locks the accusation and stores a server timestamp. The mystery panel grades objective answers and identifies the earliest correct killer + weapon.

Check reasoning and proposed prevention; tell facilitator which fixes merit credit. Captains do not apply mystery credits or manually timestamp forms.

Lock; reveal the story on slides. Tick good fix/prevention rows in the mystery panel → Apply mystery credits ONCE. Earliest correct bonus is included by the grader; do not add it again.

Switch to Azure Demo controls after the mystery reveal. Show Healthy baseline → Deploy Dave: pool 50 → 5 → Launch surge.

Students watch the failure and may place a Google-authenticated Demo order if asked.

Demo creates real simulated orders, waits and timeouts; it does not score the Live mystery.

Keep Live teams focused on the difference between prepared evidence and the real app; no score entry.

Stop new traffic → Healthy / Roll back; demonstrate recovery. Return to Live and take the 11:00–11:15 break.

Run → Observability Treasure Hunt → Launch. Drive the prepared tool/demo screen; read questions and let teams suggest where to look.

Teams record all 15 answers and proof from what they see; COO submits the team form and reflection.

Stores answers + proof, not an authoritative self-marked total. Some tool questions need a rehearsed environment; use prepared evidence if unavailable.

Review answers and proof against the question rubric. Propose up to +150, explaining disputed items.

Workshop → Apply once on reviewed credits; optional strong reflection bonus +20 via Leaderboard with reason. Do not use Apply self-marked totals as a substitute for review; no second duplicate award.

Run → Error Budget Poker → Launch. Read each card; for cards needing chance, click Issue immutable staff rolls for this card before submission.

Team discusses A/B; SRE advises on budget and CTO checks frozen design. COO submits the final choice and issued roll.

Uses immutable staff rolls and frozen design; saved decisions are final. Shows running budget and card outcomes.

Confirm design evidence and help teams reason; do not create local dice rolls or adjust the computed scores.

Next card through End the month → Apply final credits ONCE. Discuss tradeoffs; Lock / End. Keep all forced card consequences even in a shortened round; lunch 12:40–13:25.

Run → Blameless postmortem → Launch; start a 12-minute timer and emphasize systems, not blame.

Team writes summary, impact, timeline, root cause and actions with owner roles/dates; COO submits.

Stores the complete report, available to captain review.

Choose region best based on blameless reasoning and concrete actions; approve +40 for that team.

Apply once for regional reviews; choose the overall best and add +75 in Leaderboard with reason. Read useful actions aloud; End.

Run → Digital Delivery Factory → Launch. Workshop → Start round 1 for three minutes → Stop; then Start round 2 → Stop.

Round 1: COO processes tickets serially. Round 2: CEO plans, CTO builds, SRE tests, COO deploys concurrently. Failed tests return to Build.

Records tickets, successful releases, lead time, failures and recovery; Workshop displays round comparisons.

Pick region winner: most successful round-2 releases, then fewer failures, then lower lead time; approve +50.

Apply once on factory reviews. Explain DORA teaching proxies, then show the CI/CD slide or a separately rehearsed pipeline. No paper planes.

Teach the security/cost concepts; Run → Cloud Bill Shock → Launch on phones.

Team gets three digitally dealt cards; CFO reads costs and CTO checks the frozen design. COO selects preventing controls and submits.

Deals reproducible cards from session/team, evaluates frozen design and correct controls; displays the computed total.

Help students interpret cost controls; no paper-card draw or arbitrary refund decision.

Lock → Apply bill credits ONCE. Discuss painful surprises. Scores may decrease. End; break 15:00–15:10.

Run → Follow the Order → Launch. Workshop → Station games → Follow the Order; assign the seven volunteers and Start order ticket.

Assigned volunteers read their business-system cards and hand off only when their station is current; others follow the story.

Records timestamped handoffs; Workshop lets facilitator Block / simulate outage and Recover / resume.

Support volunteer positions and explain the business meaning of each handoff; no default point review exists for this activity.

Block the order, discuss impact, recover it and show queued progress. Connect to the Demo ERP outage only if rehearsed; End. Any discretionary bonus needs an explicit Leaderboard reason.

Use digital career cards in My workshop, then Run → My 90-day cloud plan → Launch; reserve time for questions.

EVERY student chooses a target role and submits their own 30/60/90-day steps; peers can discuss and swap career ideas.

Stores each individual plan; it remains accessible from My workshop.

Check all five members have a meaningful plan; support placement/internship goals.

Review/export plans as needed, Lock / End, then Q&A. This is not a shared COO team submission.

Run → Day 2 recap quiz → Launch; use the Live projector screen.

Team discusses; COO taps one answer per question.

Stores team answers and scores each revealed question once.

Help missing teams participate; no separate quiz award review.

Lock answers → Reveal and score → Next question. After question 10, verify the Live leaderboard and End.

Run → Demo Day: region vote → Launch after regional 90-second CEO pitches.

COO votes for another team in the region. Four finalists pitch on stage for three minutes each.

Tallies regional votes; this activity has award = 0, so it does not add points.

Time and judge regional pitches; help resolve ties and invite the finalists.

Lock; pick Most Creative Pitch from the grand final. Record the award in Workshop; do not invent a +50 award from the zero-credit vote.

Close entry collection after announcing a deadline; inspect captain-shortlisted X links with #ChaiCartCloudWorkshop. Show final Live leaderboard.

Submit their best optional public X post link in My workshop before the deadline; ask consent before sharing photos.

Keeps entries and shortlists; Workshop records the named award recipient. Recording an award does not change credits.

Shortlist entries for learning value, creativity and workshop spirit; check regional standings and disputes.

Choose one individual Best Workshop Post or Photo winner and other awards. Record each intended recipient in Workshop; team champion labels currently require selecting a registered student representative.

Run → Post-workshop feedback → Launch; give students time to finish. Verify attendance before issuing certificates.

EVERY student submits feedback, compares confidence and signs in to InspiredLearning with the same Google account for their permanent results and certificate.

Stores individual feedback; the portal announcement links to InspiredLearning; certificates require individually verified completion.

Check missing feedback; verify regional attendance in InspiredLearning and direct students to their permanent account.

Finish scores and awards, then Workshop → Mark workshop complete. Open InspiredLearning → Workshop staff; import older registrations, verify attendees and mark absentees, then publish verified results. Completed learners receive an authenticated certificate and 100 learning points once, separate from workshop credits. The Live portal announcement does not issue certificates. Review every learner before deleting a completed session.