Skip to content

Latest commit

 

History

History
90 lines (58 loc) · 5.33 KB

prereq_instructor.md

File metadata and controls

90 lines (58 loc) · 5.33 KB

Instructor Preparation

Time-box

N/A: these preparatory steps should be completed prior to the start of the course.

Overview

This section is intended for the workshop instructor. It outlines what the instructor should do to successfully execute this workshop. (Are you a Student? Go here: Student Preparation)

This workshop is intended to be as 'hands-on' as possible. While some lecture and demonstration is necessary, the focus is on having participants spend the majority of their time working on using the skills demonstrated. As such, the workshop focuses on the following:

  • Short sections of lecture to elaborate on the what and the why
  • Short demos to show participants what to do and what to expect
  • Hands-on practice labs to enable participants to practice all the skills in a supportive environment
  • Side-saddle mentoring and question answering
  • Pair programming to enable participants to help each other
  • For face-to-face events, we strongly recommend the teaching practices suggested by Software Carpentry, including: sticky notes, minute cards, one up/one down, students using their own machines, collaborative note taking, pair programming, and the peak rule. For details on these, see this Software Carpentry article

What to do

There are two ways to run this workshop... a short codeless format OR a longer version based on a coding project.

Codeless Format:

The Codeless Format can generally be handled in ~2 hours and doesn't require any code writing, but does include some commandline usage and covers git, GitHub, etc.

Duplicate the repository we will be using for the workshop, via the following steps:

  • Log-in to GitHub (create a GitHub account if you don't have one already) and navigate to chalmerlowe/intro_to_sprinting_codeless_project. This project is full of poetry/short stories.

  • [NOTE: in this step, Do Not fork the repository, you want a completely separate copy of the project]

    Duplicate the project into a new project of your own under your account. See: Duplicating a repository

Coding Project Format:

[NOTE: The details of the Coding Project Format are still in the works, so your mileage may vary]

For Python-focused developers, a calculator-based project is under development that can be used to expand the workshop to a total of ~4 hours and allow the participants to learn more about Sprint experiences such as testing, continuous integration, code formatting, etc.

IF you wish to experiment with a Coding Project Format and don't already have one in mind, do the following:

Duplicate the repository we will be using for the workshop, via the following steps:

  • Log-in to GitHub (create a GitHub account if you don't have one already) and navigate to seawolf42/python-rpncalc

  • Duplicate the project into a new project of your own (do not fork, you want a completely separate copy of the project)

  • [NOTE: in this step, Do Not for the repository, you want a completely separate copy of the project]

    Duplicate the project into a new project of your own under your account. See: Duplicating a repository

  • [NOTE: For more information specific to the rpncalc project, see the Instructor ReadMe]

Other pre-workshop reminders

  • Secure a location with a projector, tables, chairs, whiteboard, etc
    • Don't forget to reserve the room starting about an hour prior to the start of the session so you have time to confirm everything is working as expected
  • Advertise the session and process registrations, waitlist, etc
  • Plan for food and beverages (the workshop is ~two to four hours in length depending on the format)
  • Set up an online collaboration channel where participants can share resources, ideas, etc. Etherpad
  • Acquire supplies: red/green post-it notes, pencils, markers, etc

At the venue

  • Set up the projector, tables, chairs
  • Pick up any food/beverages
  • Distribute the red/green post-it notes and pencils to each student
  • Time allowing, open the room as early as possible so that students can start installing prerequisites

Post workshop follow-up

  • Thank the attendees for their participation
  • Issue a post-workshop survey (i.e. using Surveymonkey.com OR Google forms)
  • If you have suggestions OR found something that just doesn't work: submit an issue to the repo Intro to Sprinting Workshop OR
  • Better yet, work with your students to have them submit a Pull Request with suggestions or improvements

Resources

N/A

Previous Up Next
Course Overview and Preparation Course Overview and Preparation Student Preparation