Presenter’s want feedback => state what kind fo feedback you want
- Identify any questions you have about your process or handouts
- tell us about your concerns ( so we can watch for you)
- observers should bring their perspective to the observation + make suggestions
Provide context for lesson (what the class has learned so far and how your lesson fits in)
Provide overview of the lesson with reference to the printed lesson
Point out any areas you are concerned about => and TEACh those (walk through the language or activities you will use)
Discussion
I think you are all well prepared for your lessons - and am looking forward to hearing your reports.
Commenting on student writing.
During the second half of class we through strategies for assessing, and commenting on student writing.
We began by acknowledging that assessment has different purposes: evaluating (as in giving grades and deciding how/whether programming/teaching is working = summative assessment; and giving feedback on how to move forward = formative assessment. Most of our discussion focused on formative feedback for student writing.
Strategies for commenting on student writing: Clark observes that many issues in student writing can arise from incomplete or confusing directions for writing assignments. She pointed out that the audience, purpose, form, and style for writing assignments needs to be clearly set forward so that students can make appropriate decisions about what to write.
In light of this comment, I described the expectations for audience, purpose, and form for the writing posted on the last blog, and we developed a rubric for summative evaluation of that writing. We then assessed the summaries in light of that rubric and found that we generally ranked the essays in the same order, and that overall we had similar reasons for that ranking (though not exactly the same). We also found that we assigned different grades. This led to a discussion of what grades are meant to meaure (effort? level of competence? completion of requirements?) and the difference between giving a grade and providing feedback.
I passed out the Sommers book on commenting - though we didn't talk about it - and set you up to comment on papers for next class.
For next class:
1. Keep posting to your course blogs (observations of your mentor's class).
2. Grade + provide comments for 5 papers from a set of papers from your class. Make sure to include a range of writing issues and levels of proficiency.
We will begin by hearing your reports on your lessons and doing some debriefing (what went well, what you want to work on, and brainstorming for how to do that work).
We will then spend some time discussing effective comments to student papers. Remember that one of the components of your portfolio is a sample of "graded" papers - so this would be a start on that.
Finally - we will spend some time talking about observations (another component of the portfolio). We are going to do a rhetorical analysis for the kind of observation you want to include - and cruise around some web sites on writing observations.
See you next week.
I think you are all well prepared for your lessons - and am looking forward to hearing your reports.
Commenting on student writing.
During the second half of class we through strategies for assessing, and commenting on student writing.
We began by acknowledging that assessment has different purposes: evaluating (as in giving grades and deciding how/whether programming/teaching is working = summative assessment; and giving feedback on how to move forward = formative assessment. Most of our discussion focused on formative feedback for student writing.
Strategies for commenting on student writing: Clark observes that many issues in student writing can arise from incomplete or confusing directions for writing assignments. She pointed out that the audience, purpose, form, and style for writing assignments needs to be clearly set forward so that students can make appropriate decisions about what to write.
In light of this comment, I described the expectations for audience, purpose, and form for the writing posted on the last blog, and we developed a rubric for summative evaluation of that writing. We then assessed the summaries in light of that rubric and found that we generally ranked the essays in the same order, and that overall we had similar reasons for that ranking (though not exactly the same). We also found that we assigned different grades. This led to a discussion of what grades are meant to meaure (effort? level of competence? completion of requirements?) and the difference between giving a grade and providing feedback.
I passed out the Sommers book on commenting - though we didn't talk about it - and set you up to comment on papers for next class.
For next class:
1. Keep posting to your course blogs (observations of your mentor's class).
2. Grade + provide comments for 5 papers from a set of papers from your class. Make sure to include a range of writing issues and levels of proficiency.
We will begin by hearing your reports on your lessons and doing some debriefing (what went well, what you want to work on, and brainstorming for how to do that work).
We will then spend some time discussing effective comments to student papers. Remember that one of the components of your portfolio is a sample of "graded" papers - so this would be a start on that.
Finally - we will spend some time talking about observations (another component of the portfolio). We are going to do a rhetorical analysis for the kind of observation you want to include - and cruise around some web sites on writing observations.
See you next week.