class: middle, centre background-image: url(lecture1.jpg) background-size: cover .bigtext[Induction Session for Maths Lecturers] --- # Outline * Ethos and Expectations * Lectures: General Aims * Before the Lecture itself / Preparation * The Lecture -- some tips * Aligning the course / Problems and solutions * After the Lecture / Support --- # Ethos and Expectations * Department will * Provide students with a research-led education in mathematics, training them as part of a community of professional practice. * Provide opportunities for students to develop further their general skills in communication, problem-solving, critical thinking, and the ability to work independently. --- # Ethos and Expectations * Students will * Engage actively with the learning opportunities provided for them. * Take responsibility for their own learning, working to understand material through independent study and practicing skills through assigned exercises. --- # Rule of thumb:
everything is your fault. --- class: middle, centre background-image: url(lecturer-shepherd.jpg) background-size: cover .bigtext[Lectures: General Aims] --- # Aims of lecture courses * Provide framework on which the students build their understanding * Usually they will be building notes based on your lectures and problems * You are their guide over 20 / 40 lectures * You provide support so they can all follow * You are responsive (quickly) to their needs and requests * Remember: most of our students are kind and reasonable! --- class: middle, centre background-image: url(lecture_prepared.jpg) background-size: cover .bigtext[Preparation] --- # Preparation (Course) * Figure out what the students know and their level * At the beginning, follow closely what was done before * Don't try to do it from scratch unless you are very experienced * Don't try to put in too much material!!! * You will need to pace the course so the weakest can follow * But add extra to entertain strongest * If you lose 5% each lecture then after 1 term you will have ~ 35% following! --- # Preparation (Lectures) * (Re)Prepare as course goes along (align set problems with the week's lectures) * Figure out (from discussion with the students) what they need. Do they need you to go over something? Did they ask for more examples? * Think of how to make your examples interesting and useful --- # Preparation (Lectures) * Prepare your proofs * Don't be tempted to wing it in real time - trivial mistakes will be seen as signs of incompetence. * Prepare your board use (write a "master board" in the lecture? Number parts of proof? Diagrams to orient students?) * Work out your timing. --- # Preparation (Supporting material) * You will need questions to accompany course + solutions * Your lectures should be aligned with them (and also exam questions) * Use Ultra to deposit lecture notes, problem sets and solutions, and to provide **lecture plans**, links, announcements etc. * It will get carried over next year * Arrange weekly office hours --- class: middle, centre background-image: url(lecturer-alignment.jpg) background-size: cover .bigtext[ Alignment] --- # Alignment * Be mindful of the learning route the students are on * Set questions each week for students to develop their understanding of what you teach * Ideally after each lecture the students will try relevant questions * Set some basic (/predictable) questions and then stretching (/less predictable) questions * The questions make a good basis for recap in lectures --- class: middle, centre background-image: url(lecturer-tucker.jpg) background-size: cover .bigtext[Lecturing - some tips] --- class: middle, centre background-image: url(lecturer-tucker.jpg) background-size: cover .white[Do you understand the words ] .white[that are coming out of my mouth?!] --- # In the lecture (patronizing advice) * You are in control! You may have to shepherd them in * Be punctual: start at 5 past, stop at 5 to the hour * Lecture recordings: Encore automatically records sound and anything projected --- # In the lecture * Work out the tech before you get there (emergency IT help button on phone) * Wear a portable microphone * University policy is to have pens that never work, so bring your own * Take command of the room and prepare for moderate crowd control. If you don't do this half of the students will complain due to the other half, but it's still your fault. --- # In the lecture * Recap previous lecture briefly at the beginning * Build a rapport over the weeks: be approachable and don't get upset * Explain it to them as if you are talking to a single person * DON'T assume they must already know it - they don't --- # In the lecture * Engage with them: make eye-contact. Are they following? Do any look confused? Do not just ask if they are following, ask questions! * Speak/write slowly enough that they can take notes (wait if still writing) * Speak to the back of the room * Write big - ask the back of the room if they can read it * Arrange board use so rubbing out of stuff is delayed as long as possible * Rubbing out is a great time to ask for questions --- # In the lecture (questions) * Great you got a question: someone engaged! * Give them credit for having spoken ("great question!") * There are no "dumb questions" (if you think so, it's your problem) * Go back to where they got confused * Consider covering background if it seems they need it --- # In the lecture (tips) * Pause for questions regularly (wait 10 s) * At the end of each topic / lecture: recap, outline what's next, and encourage questions * Better to stop early than rush to cram stuff in * Wipe the board and be available to answer questions, but leave the room by the hour * If you want advice, ask your mentor to observe you --- class: middle, centre background-image: url(lecturer-support.jpg) background-size: cover .bigtext[Support] --- # Support your students * Be approachable and available after the lecture (subject to timetable) * Arrange weekly office hours to meet students (poll them to find a time?) * You can also use email and Ultra discussion boards to answer questions - your call. * If there is a particular issue, adapt your plan and address it. It saves you time in the end. --- # Questions?