Instructor Guide


January

  • [Instructor] Update the course website with registration info, put warnings on schedule, and hide assignments.
  • [Instructor] Set up the Brightspace page with registration instructions.
  • [Instructor] Check that the room has been scheduled in mytimetable.
  • [Instructor and Coordinator] Meet to plan this year.
  • [Instructor] Schedule Brightspace announcements for registration.

February

  • Registration opens Feb 1.
  • [Coordinator] Advertise the course in flyers, coffee machine screens, etc.
  • [Coordinator] Manage registrations and wait list.
  • [Coordinator] Write to guest lecturers and ask for their participation. Give an idea of what dates work best for us.

March

  • Regsitration closes Mar 1.
  • [Coordinator] Send out confirmation of course registration.
  • [Instructor and Coordinator] Check-in meeting about registration and planning between instructor and institute.
  • [Instructor] Reserve the Cosmed for the expected days we will need it.

May

  • [Coordinator] Final confirmation with team members. Add team members to reduce chance of no shows on first day.
  • [Instructor] Find a teaching assistant.
  • [Coordinator] Hire the teaching assistant.
  • [Instructor] Finalize the schedule and update the website.
  • [Instructor] Meet with teaching assistant and share all info. Add TA to shared folder and github and brightspace.

June

  • [Instructor] Finalize schedule and post to the website.
  • [TA] Order any Cosmed consumables we need.
  • [Instructor] Move last years releveant files to this year's google drive and share with the teaching assistant.
  • [Instructor] Create new MS Teams.
  • [TA] Add groups and private channels to MS Teams. Make sure everyone can access.
  • [TA] Get trained on using the Cosmed system (ideally from the lab coordinator).
  • [TA] Test the physio test completely with someone and get sample data to provide to the students.
  • [TA] Book the BHV (first aid) person to be present during physio tests. Call around to companies, least cost if possible. Arrange invoicing with Coordinator.
  • [All] Meet one week before class starts to review all outstanding information and issues.
  • [TA] Make attendance sign in sheets for each day and manage this through the two weeks.
  • [Instructor] Send out welcome emails to both students and lecturers with basic course info.
  • [TA] One week before, test out a full physio experiment with the Cosmed.
  • [TA] Gather up all experimental equipment we may need and organize it a tote we can carry to the classroom, sports hall, and velodrome. Use the bike lab checkout system.

Github

https://github.com/moorepants/me41035

  • Public course website is managed here.
  • Issue tracker is used for tasks and such.

Brightspace

Only using for announcements to TU Delft students.

Course Email List

There is a list of participants and their email address. Announcements can be made via email to announce to all involved.

Sports Institute Coordinator Responsibilities

  • managing registrations
  • forming teams
  • ask lecturers for participation
  • booking the X hall
  • booking the velodrome
  • booking the bus to the velodrome
  • organizing a social with a speaker

TA Responsibiilties

  • collect the lecture slides from the lecturers and upload them to MS Teams ASAP
  • learn to use the cosmed
  • book the first aid company for the physio testing
  • organize and perform the physio testing
  • managing any equipment used from the bike lab, finding out what students may need, making sure anything expensive is handled with care, being generally present and helpful
  • helping answer questions during office hour sessions
  • presence during the experiment sessions
  • presence during reporting on the assignments and spinning the random wheel to call teams to present
  • assisting instructors with the assessment of the assignments (giving written feedback on the reports in the evening, one day turn-around usually)
  • making presentation schedule (or random wheel)
  • setup meetup for hybrid lectures if needed (usually one lecture has to be online)
  • organize the social activity on the last Friday. We've done bowling, mooie boules, beach volleyball, etc. Note that collecting money from everyone at the end (tikkie, for example) does not always go well. Best to get upfront buy in if possible.

Forming teams

  • Only students who are actually enrolled will participate in the team work for the assignments. (students list in the roster spreadsheet)
  • Teams should be made up with 4 people ideally, but can be 3 or 5 if necessary. We have a max of 45 students and thus can do 9 five person teams. That is about our limit. Having 8 teams might be preferrable.
  • The teams should maximize the mixture of students from the different universities, otherwise random selection.
  • Form the teams prior to the first day so that we can post the team list with contact info on the first day. Make a PDF contact list showing the teams and their emails.

Office hours

  • All instructors and teaching assistants should be present to help answer questions during these scheduled time periods.
  • On the physical testing days we can split between the X hall, bike lab, and/or classroom.

Assignment reporting

  • After each assignment the teams give a presentation.
  • A subset of the team can speak in the first two lighting presentations. All students in the team must speak in the last presentation.
  • Ask a question if students in the room do not ask questions.
  • Prepare a timer to be strict on lightning talk time limits and have a way to randomly select teams if there are no volunteers.

Final Presentations

We have 2 hours to do the final presentations. 6 minute presentation per team + 5 min Q & A. We do these in a booked room across the street from the velodrome.

Setting up MS Teams

  • The Sports Engineering Institute coordinator registers all students and forms them into teams. They place the roster with team assignments in the shared drive.
  • The TA makes team names for the year and adds those to the roster spreadsheet.
  • TA then adds each student as a member to the MS Team.
  • TA creates private channels for each group and names the channel the group name and adds the correct team members to the group.
  • It may be best to do this after the first day because sometimes there is some shuffling of people on teams.

Monday "Meet Your Team"

We need to bring a ball, frisbee (soft preferably), or some other thing to toss.

  • Get in big circle.
  • Each person says their name with an adjective with matching first letter: "Jumping Jason" and they should do the action, i.e. Jason jumps up and down.
  • Now toss the ball to a person and the ball tosser says the person's name they toss to.
  • Keep going until everyone catches the ball and their name is said again.

Monday "First Team Assignment"

Things to bring:

  • Need tape/stickers to stick on ground
  • Need a way to lift the table slightly to make the table into a sloped ramp
  • Try to get some new bouncy tennis balls (borrow preferably)

Notes on MS Teams

  • Create a "Team" and select "Class" as the type.
  • This team can have channels, for example one for each group in the class to chat, discuss, and meet in. There is a default general channel.
  • Guests that don't have tudelft.nl email addresses can be added by adding a member and typing their email address. They'll get an email notification to log into team with their personal MS account. They'll be a "guest" when the log in that has fewer permissions than tudelft.nl people, but from the student perspective it shouldn't be different. If we want to give John Hart more permissions it might matter.
  • Breakout groups is missing on Linux, so Jan will have to handle that if we need it., But we may be able to make a channel for each group and we can hop into the group's channel to help them.
  • John had trouble logging in on his first attempt. With the error: > Invitation redemption failed > AADB2B_0001 : We cannot create a self-service Azure AD account for you > because the directory is federated. Tenant’s admin must create an account for you.
  • Doesn't look like I can send a single url for people to join the team (at least not the people outside TUD), but that I have to add them directly to the team and they will get an email invite.
  • Looks like we can schedule meetings associated with the team, so we can also get an access link and have them show up in people's calendars (probably).