Skip to content

Latest commit

 

History

History
342 lines (275 loc) · 14.7 KB

File metadata and controls

342 lines (275 loc) · 14.7 KB

Delivery Logistics Checklist

Overview

This checklist supports in-person delivery of the 12-session GitHub training curriculum for farmers. Each session runs 165 minutes (2h45m with 15-minute buffer). Use this document to prepare the venue, test technology, organize materials, and handle session-day logistics.


1. Venue Setup (Day Before)

Complete these tasks 24 hours before the session:

Room Layout

  • Arrange seating in U-shape or classroom style for 15-20 learners
  • Position instructor table at the front with clear sightlines to projector screen
  • Leave 3-4 feet of walkable space around perimeter for instructor circulation
  • Set up tables to accommodate laptops (minimum 24 inches width per learner)
  • Verify all seats have clear view of projected screen

Power and Connectivity

  • Test all wall outlets in the room
  • Position 3-4 power strips around the room (one per 4-5 learners)
  • Run extension cords safely along walls (tape down cables to prevent tripping)
  • Label power strips with table numbers or seat ranges
  • Verify instructor table has dedicated power outlet for laptop and projector

Display Equipment

  • Set up projector or large screen display
  • Test projector connection with instructor laptop (HDMI/VGA/USB-C adapter ready)
  • Adjust projector focus and keystone correction
  • Position screen at appropriate height (top of screen at or above seated eye level)
  • Verify screen is readable from back row

Network Access

  • Test Wi-Fi connectivity in all corners of the room
  • Note Wi-Fi signal strength at back tables
  • Write Wi-Fi network name and password on whiteboard or flip chart
  • Confirm network supports 15-20 simultaneous connections
  • Identify backup mobile hotspot device and confirm data plan active

Workspace Tools

  • Set up whiteboard or flip chart at front of room
  • Stock dry-erase markers (test 3-4 to ensure they work)
  • Provide eraser or paper towels for whiteboard
  • Post blank chart paper on wall for parking lot items

2. Technology Checklist (1 Hour Before Session)

Complete these tasks 60 minutes before learners arrive:

Instructor Laptop

  • Fully charge laptop (bring power adapter to session)
  • Connect laptop to projector and verify display mirroring
  • Set screen resolution to 1920x1080 or lower for projector compatibility
  • Increase browser zoom to 150% minimum for readability from back row
  • Disable sleep mode and screen dimming during session
  • Close all unnecessary applications to reduce distractions

Browser and GitHub Setup

  • Open browser with all session-specific demo repositories bookmarked
  • Log in to instructor GitHub account
  • Verify demo repository is in expected state for the session
  • Test GitHub page load speed on venue Wi-Fi
  • Clear browser cache if pages load slowly
  • Open facilitation script in second browser tab or separate device

Backup Preparations

  • Copy session slides to USB drive
  • Save offline screenshots of critical demo steps to laptop desktop
  • Verify mobile hotspot device is charged and ready
  • Test screen mirroring from phone to projector (if projector fails)
  • Download PDF copies of all session handouts to laptop

Communication Settings

  • Silence phone and place in Do Not Disturb mode
  • Disable all laptop notifications (email, calendar, messaging)
  • Turn off automatic software updates
  • Close Slack, email clients, and social media tabs

Audio/Visual Test

  • Project first slide and verify readability from back row
  • Walk to back of room and confirm text is legible
  • Adjust lighting to reduce glare on screen
  • Test any video clips or animations in slides (if applicable)

3. Printed Materials (Per Session)

Per-Session Print Matrix

Print the following materials for each session. Use this table to prepare handouts:

Session Core Materials Reference Guides Copies Needed
1 Lab exercise, Terminology cheat sheet Terminology cheat sheet Learners + 3
2 Lab exercise Issue creation guide Learners + 3
3 Lab exercise, Project board checklist Project board checklist Learners + 3
4 Lab exercise Collaboration basics guide Learners + 3
5 Lab exercise Notification settings guide Learners + 3
6 Lab exercise Template design guide Learners + 3
7 Lab exercise Actions overview guide Learners + 3
8 Lab exercise Workflow setup guide Learners + 3
9 Lab exercise Advanced projects guide Learners + 3
10 Lab exercise Copilot getting started guide Learners + 3
11 Lab exercise Spark agents guide Learners + 3
12 Lab exercise, Capstone guide Capstone guide Learners + 3

Print Distribution Checklist

  • Count learner registrations and add 3 for extras
  • Print all session-specific lab exercises (one per learner)
  • Print reference guides for the session (one per learner)
  • Print L1 evaluation survey forms (one per learner)
  • Collate materials into session packets (staple or clip by learner)
  • Label extra copies for latecomers or damaged handouts

One-Time Print Materials (Session 1 Only)

  • Print terminology cheat sheet for all 12 sessions (one per learner, laminate if possible)
  • Print sign-in/attendance sheet template
  • Print emergency contact information for venue coordinator
  • Print Wi-Fi troubleshooting guide for common device types

Evaluation Forms

  • L1 reaction surveys (print one per learner, every session)
  • L2 observation rubrics (instructor copy, every session)
  • L3 behavior surveys (print for Sessions 4, 8, 12 only)
  • L4 results surveys (print for Session 12 only)

4. Instructor Preparation (Per Session)

Complete these tasks during the week before each session:

Content Review

  • Read facilitation script for the session end-to-end
  • Review slides and identify any updated screenshots or content changes
  • Note timing estimates for each segment (lecture, demo, lab, debrief)
  • Identify potential challenge points based on previous session feedback

Demo Walkthrough

  • Execute all demo steps on live GitHub (not from memory)
  • Verify demo repository matches the expected starting state
  • Test each click-through path and confirm UI matches slides
  • Note any GitHub UI changes that differ from slides
  • Prepare alternative explanations for steps that may confuse learners

Lab Exercise Preparation

  • Complete the lab exercise yourself as a learner would
  • Time yourself completing each step to validate time estimates
  • Identify steps that may require additional clarification
  • Prepare 2-3 troubleshooting tips for common issues
  • Verify lab instructions match current GitHub UI

Backup Content

  • Take fresh screenshots of all critical demo steps
  • Save screenshots to laptop desktop in a session-specific folder
  • Prepare offline discussion questions in case of internet failure
  • Review printed handouts to ensure they can substitute for online demos

Grouping and Engagement

  • Decide if table groupings are needed (pairs or small groups)
  • Prepare name tents or table markers if using group assignments
  • Identify 2-3 discussion questions for breaks or early finishers
  • Plan cold-call rotation to ensure all learners participate

5. Day-of Procedures

Arrival (45 Minutes Before Start)

  • Arrive at venue 45 minutes before session start time
  • Unlock room and turn on lights
  • Complete all items in Section 2 (Technology Checklist)
  • Set room temperature to comfortable level
  • Place sign on door with session name and start time

Learner Welcome (30 Minutes Before Start)

  • Set up sign-in sheet at entrance table
  • Greet learners as they arrive and direct them to seating
  • Distribute session handout packets
  • Write Wi-Fi credentials on whiteboard in large print
  • Provide verbal Wi-Fi instructions for those who need help

Pre-Session Setup (15 Minutes Before Start)

  • Post session agenda on whiteboard or flip chart
  • Write session timing on whiteboard (start time, break time, end time)
  • Set visible countdown timer on screen or desk clock
  • Test projector one final time
  • Remind early arrivals to log in to GitHub before session starts

Session Start

  • Begin precisely on time (respect learners' schedules)
  • Welcome learners and introduce yourself
  • Review session objectives and agenda
  • Confirm all learners can see screen and access Wi-Fi
  • Explain attendance tracking and evaluation process

During Session

  • Start visible timer for timed activities (lab exercises, small group discussions)
  • Circulate during hands-on activities to provide individual support
  • Monitor learner progress and adjust pacing if needed
  • Use parking lot flip chart for off-topic questions or technical issues
  • Provide 5-minute and 1-minute warnings before transitions

Session Close

  • Distribute L1 evaluation surveys 10 minutes before end time
  • Collect completed surveys before learners leave
  • Preview next session topic and homework (if any)
  • Thank learners for participation
  • Remind learners of next session date and time

6. Emergency Procedures

Internet Failure

  • Switch to backup mobile hotspot immediately
  • Announce network change and provide new credentials
  • If hotspot also fails, transition to offline screenshots mode:
    • Project saved screenshots from laptop desktop
    • Walk through demo steps using static images
    • Shift to discussion-based activities using printed handouts
    • Shorten lab exercise and extend debrief discussion

Projector Failure

  • Attempt to reconnect laptop to projector (check cable, reboot projector)
  • If projector cannot be fixed, use contingency plan:
    • Gather learners in small groups around instructor laptop
    • Rotate groups every 10 minutes so all can see demos
    • Increase reliance on printed handouts
    • Pair learners for lab exercises and rely on peer support

GitHub Service Outage

  • Check GitHub status page (status.github.com) on phone
  • Announce outage and estimated restoration time
  • Redirect to printed materials and discussion activities:
    • Facilitate group discussion of session concepts
    • Use whiteboard to draw workflows and processes
    • Conduct verbal walkthroughs of lab steps
    • Assign reading of reference guides with group discussion
  • Offer makeup lab session if outage is prolonged

Learner Device Failure

  • Pair learner with neighbor for screen-sharing observation
  • Provide observer mode guidance:
    • Watch neighbor's screen and discuss each step
    • Take notes on printed lab exercise
    • Ask neighbor to slow down for note-taking
    • Offer to complete lab exercise at home after session
  • If multiple devices fail, check Wi-Fi and provide troubleshooting
  • Offer instructor laptop for critical demonstrations if needed

Medical Emergency

  • Call venue emergency contact or 911 if serious
  • Designate another learner to assist if needed
  • Pause session until situation is resolved
  • Resume or reschedule session based on severity

Severe Weather or Evacuation

  • Follow venue evacuation procedures
  • Ensure all learners exit safely
  • Announce rescheduled session date via email after event

7. Post-Session Procedures

Immediate (Within 15 Minutes of Session End)

  • Collect all L1 evaluation surveys
  • Count surveys to verify all learners submitted
  • Note any immediate feedback shared verbally by learners
  • Complete L2 observation rubric while session is fresh in memory
  • Pack up all materials and equipment

Documentation (Same Day)

  • Review L1 surveys and identify common themes
  • Transfer L2 observation notes to digital format
  • Document any technical issues or disruptions:
    • Internet connectivity problems
    • GitHub UI discrepancies from slides
    • Projector or equipment failures
    • Timing issues (segments too long or too short)
  • Note questions or confusion points that need clarification in future sessions

Instructional Adjustments (Within 24 Hours)

  • Update facilitation script with lessons learned
  • Flag slides that need revision based on learner confusion
  • Adjust timing estimates if segments ran long or short
  • Document alternative explanations that worked well
  • Share feedback with curriculum development team

Demo Environment Reset (Before Next Session)

  • Verify demo repository is ready for next session
  • Reset any modified issues, projects, or workflows
  • Create new test data if consumed during current session
  • Update screenshots if GitHub UI has changed

Preparation for Next Session

  • Review post-session feedback before planning next session
  • Incorporate adjustments into next facilitation script
  • Print materials for next session (see Section 3)
  • Schedule makeup session for absent learners if needed

Checklist Completion Notes

Use this section to document completion dates and issues:

Session Date Delivered Venue Setup Complete Tech Test Complete Materials Printed Issues Encountered
1 _____________ _____ _____ _____ _________________
2 _____________ _____ _____ _____ _________________
3 _____________ _____ _____ _____ _________________
4 _____________ _____ _____ _____ _________________
5 _____________ _____ _____ _____ _________________
6 _____________ _____ _____ _____ _________________
7 _____________ _____ _____ _____ _________________
8 _____________ _____ _____ _____ _________________
9 _____________ _____ _____ _____ _________________
10 _____________ _____ _____ _____ _________________
11 _____________ _____ _____ _____ _________________
12 _____________ _____ _____ _____ _________________

Additional Resources

  • Venue Contact: _______________________________________________
  • Venue Emergency Procedures: _______________________________________________
  • IT Support Contact: _______________________________________________
  • Backup Instructor Contact: _______________________________________________
  • Curriculum Coordinator: _______________________________________________

Version History

  • v1.0 (2026-01-30): Initial checklist created for 12-session GitHub training curriculum