Integration Guide

Network Configuration Day

Pre-work (assigned previous day): Watch 20-min video on TCP/IP basics, read article on subnet masks, complete 5-question knowledge check.

Class opening (9:00-9:25): Check-in on pre-work with questions: “What’s the difference between a switch and a router? When would you use each?” Based on responses, spend 15-20 minutes reviewing key TCP/IP concepts. Demonstrate how to verify network connectivity using ping and traceroute, referencing what they learned in pre-work. Ask learners to predict what will happen before you run each command. “Now let’s apply this. You’re configuring a small office network. Lab 3.2 has the specs.”

Work time (9:25 onward): Learners work through the lab, applying what you just reviewed. You float, answer questions, help debug. At 10:45, notice multiple teams stuck - pause for a 10-min interactive troubleshooting session where learners explain what they’ve tried. At day’s end, quick reflection: “What was your biggest challenge today?”

React Components Day

Pre-work (assigned previous day): Watch 25-min video on React props and state, read article on component composition, complete interactive CodeSandbox exercises.

Class opening (9:00-9:30): Check understanding: “Who can explain when to use props vs. state?” Based on responses, live-code a button component for 20-25 minutes. Ask learners to predict what will happen when you change the code. Reference the CodeSandbox exercises they completed. Show common mistakes and have learners identify the bug before you fix it. “Alright, now you’ll build a product card. Lab 4.1 has the requirements.”

Work time (9:30 onward): Learners build the component, applying the patterns you demonstrated. You review their code, provide guidance. At 11:00, several teams ask about the same concept - gather everyone for a 12-min interactive discussion where teams share their approaches and you facilitate the conversation. At day’s end, reflection: “What would you refactor?”

Same Network Configuration Day, Now with Simulation

Pre-work: Same as before - TCP/IP video, subnet mask reading, knowledge check.

Class opening (9:00-9:15): Team stand-ups. Each team lead shares: “Yesterday we finished switch config. Today we’re tackling routing. No blockers yet.” You observe and track participation.

Interactive instruction (9:15-9:35): Check understanding: “From yesterday’s pre-work, what happens when a router receives a packet?” Spend 15-20 minutes reviewing TCP/IP, demonstrating ping and traceroute. Ask learners to predict outcomes, reference their pre-work. Then frame the scenario: “You’re Tier 1 Network Techs for CloudEdge Solutions. Client ticket #4472: New office needs network setup by Friday. Use what we just reviewed. Lab 3.2 is your implementation guide.”

Work time (9:35 onward): Teams work through the lab as if it’s a real client project. They apply the techniques you demonstrated, document steps in shared team doc, communicate about blockers. You coach: “How would you explain this to the client?” At 11:00, multiple teams stuck on routing - pause for a 15-min interactive session where teams share what they’ve tried and you facilitate problem-solving.

Same React Components Day, Now with Simulation

Pre-work: Same as before - React props/state video, component composition article, CodeSandbox exercises.

Class opening (9:00-9:15): Team stand-ups. Each team lead shares: “Yesterday we finished the navbar. Today we’re building the product cards. Still debugging that state update issue.” You note who’s engaged.

Interactive instruction (9:15-9:40): Check understanding: “Who remembers from the CodeSandbox - what’s the difference between props and state?” Live-code a button component for 20-25 minutes. Ask learners to predict behavior changes. Have them identify bugs before you fix them. Then frame the scenario: “You’re frontend devs at TechStart. PM just shared new e-commerce designs. Sprint goal: Reusable product card by end of day. Lab 4.1 has acceptance criteria.”

Work time (9:40 onward): Teams build the component like a real sprint, applying patterns you demonstrated. They discuss approaches, review code, update team board. You coach: “How would you present this in sprint review?” At 10:45, several teams ask about prop drilling - gather everyone for an 18-min teaching discussion where teams explain their solutions and you synthesize the patterns.

Multi-Day Security Audit Project

Monday pre-work: Read about security audit procedures and common vulnerabilities.

Monday stand-ups (9:00-9:15): Teams review weekly goals. You assign the project. Interactive instruction (9:15-9:35): Check their understanding of audit procedures from pre-work, demonstrate using a vulnerability scanner, reference their reading. Frame scenario: “CloudEdge just acquired a new subsidiary. You’re the security team. Here’s their network diagram - it’s incomplete. Audit by Friday. Requirements may change as you discover issues.”

Tuesday stand-ups: Each team reports progress: “We mapped the network, found 3 open ports. Today we’re testing for SQL injection.” Mid-morning twist: “Update: The subsidiary had a minor breach last month they didn’t disclose. Reprioritize.” Teams adjust approach, communicate changes, update documentation.

Thursday stand-ups: Teams realize they need info from another team’s findings. During work time, they coordinate, share data, negotiate priorities - just like real cross-functional work.

Friday presentations: Each team presents to you (acting as the CTO). You ask hard questions: “What’s your confidence level? What did you not have time to check? How would you handle this in a real job?”

Multi-Day Full-Stack Application Sprint

Monday pre-work: Read about RESTful API design and database normalization best practices.

Monday stand-ups (9:00-9:15): Teams review sprint goals. You assign the project. Interactive instruction (9:15-9:45): Check their understanding of REST principles from pre-work, live-code an API endpoint showing best practices, reference their reading. Frame scenario: “TechStart needs a task management app. You’re the dev team. Here’s the mockup - some features are vague. MVP by Friday. Product may change priorities.”

Wednesday stand-ups: Teams share blockers. Mid-morning twist: “Product update: We need real-time collaboration features. Users want to see changes instantly. Pivot your architecture if needed.” You facilitate a 20-min discussion where teams debate WebSockets vs. polling. They update their technical design, communicate trade-offs.

Thursday stand-ups: Frontend team mentions they’re blocked waiting for API endpoints. During work time, they negotiate priorities with backend team, create mock data, and agree on the API contract - just like real agile teams.

Friday sprint review: Each team demos to you (acting as product owner). You ask: “What technical debt did you incur? If you had another sprint, what would you refactor? How would you scale this to 10,000 users?”