Showing posts with label Social and Professional Issues. Show all posts
Showing posts with label Social and Professional Issues. Show all posts

Wednesday, July 3, 2019

Breaking up discussions: My 2019 redesign of CS 239

Although I’ve taught CS 239 (Social and Professional Issues) many previous semesters, I have not been assigned to teach it for a few semesters. Spring 2019 changed that, so I took the opportunity to revisit the learning environment I provided for the course.

This course is a one credit hour course which meets once per week for 50 minutes. Historically, I led lectures and discussions for a third to half of the weeks. I assigned the remainder of the weeks to groups of three to five students to research and present their assigned topic. Usually the group presentations consisted of lecturing, despite my encouragement to do something different.

This semester, I wanted to focus on getting the students engaged in the material. I decided to not utilize group presentations or lecturing. I focused on discussions, but also felt that keeping students engaged in fifty minutes of class discussion was a bit of a stretch. I wanted them to dig into the material and explore its importance and applicability to them as future computer scientists. With a bit of thought, I developed a plan to break each week’s fifty-minute class into a series of short discussions which focused on the week’s material in different ways.

Prior to class each week, I expected students to read an assigned chapter or topical material and find a recently published article related to it. (I called this assignment “In the News.”) Each 50-minute class session roughly followed this schedule:
  1. Announcements/reminders/questions (5 minutes)
  2. Chapter/topic quiz via clickers (10 minutes)
  3. Review/impression of the chapter/topic (18 minutes total)
    1. Assemble groups of 4 people (6 minutes)
      1. Agree on exactly 4 words (single words and/or a phrase) to describe the chapter
    2. Groups report their words (5 minutes)
    3. Groups choose one word/phrase from the accumulated list (2 minutes)
    4. Groups report back (2 minutes)
    5. Discuss common themes of (selected) words/phrases (3 minutes)
  4. In the News discussion (17 minutes total)
    1. Assemble new four-person groups (7 minutes)
      1. Very briefly discuss each person’s ItN article
      2. Select the most interesting or important article
      3. Prepare a 60 second (non-tech supported) presentation which includes:
        1. Topic and very brief description
        2. Why interesting or important?
        3. How related to the course material?
        4. Which word/phrase from above list does it relate to?
    2. Individual 60-second group presentations (10 minutes)
Thus, my objective each week was not to lecture, or directly discuss the content of the reading, but to have them engage with the material, first individually, then in small groups, and finally the full class. They first read the assigned material outside of class, and critically thought about the content as they selected a related article for the In the News assignment. Then in class, we had a short quiz, which was easy to pass if you’d done the reading, but a bit more challenging, if not. The quiz was intended to encourage coming to class prepared. If more than a few students missed a given question, we’d briefly discuss it before moving on to the next one.

After the quiz, the class split up into four-person groups to briefly discuss their understanding of the material, ultimately agreeing on exactly four words (individual words, a phrase of four words, or some other combination) which they felt represented the material. Each group reported their words, and I wrote them on the white board. After all groups had reported, I asked the groups to reconvene again, and select the one word or phrase from the accumulated list they felt best represented the material. We then briefly discussed their observations about what was, and was not, chosen.

I then asked them to form new four-person groups, where each person would very quickly summarize their selected In the News article. The group then had to decide whose article was the most interesting or most important for others to hear about. Someone (usually the student whose article was selected) from each group then reported details about the article in a one-minute presentation to the full class. (See above for the expected details.) Time permitting, we’d then have another brief discussion about their observations of the selected articles.

This format led to good—and sometimes very lively—discussion each week. The students were aware our time was limited, and thus tended to keep the discussion moving forward, rather than dwelling on one particular point. Overall, my perception of the semester was good. Most students appeared to be engaged, and willing to participate, at least in the small group discussions, if not the full class discussions. Many students were also willing to respectfully voice differing opinions, and to listen to other’s thoughts.

Rather than a final exam, the students had to write reflective responses to a few prompts. One of the prompts included (in part) the following request.
Write an essay describing, specifically, how you learned one of the items in the Top N list we created in class during our final exam time. Be specific about the context of learning: the place, the time, the people, and the process.
The class of 33 students submitted a variety of responses, some of them average. However, many responses stood out to me, and helped validate that the course had met my objective of getting students engaged with the material. I provide examples of these responses here, with the author’s permission.

Student 1:
“I have found that everyone DOES have their own ethical standards; however, it is important to adhere to the ethical standards of the field and company as well. I learned this pretty early on while going through chapter 9 about the ethics and responsibilities of professionals.; however, the ITN articles I went through really solidified the meaning for me.”
Student 2:
“In most of our discussions, if someone offered a dissenting opinion, it was often presented as an alternative way of thinking, rather than as a retort or any sort of rude negation of the presented thought. It was nice to see that a group of random students with different views were able to have respectful discourse about a variety of topics, many of which students had opposing views on.”
“This was a good opportunity to see in a real environment how even those with inherently opposing views could come to a solid and satisfactory conclusion from a “debate”, while maintaining a high level of respect for one another through the entire process. It was fitting that in a class about the professional world, we put into practice the item from the list in real life, rather than just learning about it from the text or through assignments.”
Student 3:
“This situation of disagreeing with someone’s opinion most commonly occurred on the two diversity days of class. Although the situation for me was frustrating because I felt like I couldn’t respond how I usually would outside of a classroom environment, I do think that these days were the more productive days of class because they seemed to generate the most class discussions due to the differing opinions. It was useful to be in this situation in a more professional environment because usually I am in an unprofessional environment.”
“In a professional environment, both parties are held to professional standards, whereas, in an unprofessional environment one person can be respectful, but the other person may not because of the lack of a professional environment. … The combination of these professional experiences in class and unprofessional experiences out of class helped show the differences of the same situation when people are held to professional standards or when they are not. Those differences helped cement the idea that you can have a professional conversation with two differing opinions as long as you adhere to the standards of a professional environment by being respectful.”
Student 4:
“The most prominent thing I learned was that everyone has their own ethical standards. The one moment that comes to mind that taught me this the most was early in the semester in the discussion of privacy. All four of us in the group had different opinions on what constitutes a breach of privacy. As I thought more about it later, I realized that none of us were necessarily wrong, but we just had different standards to one another. I also realized some time later that this is another argument for diversity as well, because it can help make a product that the most users will be comfortable with.”
Student 5:
“I thought everyone knew. That being said, I was proven wrong multiple times by my classmates who didn’t seem to really “get” certain concepts, like the importance of diversity or what is actually ethically sound. I sometimes found myself frustrated and wondering if I should even state my perspective because they weren’t going to “get” my point. It wasn’t until I decided that my perspective deserves to be heard just as much as the other guys that I would participate in class discussion. When I did, I remember commenting on why I didn’t agree with someone, and after I spoke someone else commented that they felt similarly to me. This gave me more confidence in my opinions, not because I knew I shared them with another classmate, but because the conversation kept going. We continued to share ideas. We didn’t stop talking just because we didn’t agree. I am often scared in conversations that if I voice my opinion either I or the person I am speaking to will let their emotions get the better of them and the conversation ends at that. With mutual respect and an open mind, even those who don’t always agree can work productively together.”
I am anxious to teach this course again using the same pedagogy to see if I get the same results. It could simply be that I had an unusual bunch of students this semester that were willing to discuss and listen to each other, and that another group of students may not do as well. I’m hoping that is not the case, as I really liked how the class worked out this time.
What are your thoughts and experiences? Please share them below in the comments.

(Edited on 07/09/2019 to add student 5's quote.)

Sunday, December 24, 2017

According to specs…


During the fall 2016 semester, I participated in a multi-session faculty learning community that explored what specifications grading is, how it might be implemented, and what it might do for our students and us. In her book Specifications grading: Restoring rigor, motivating students, and saving faculty time, Linda Nilson claims that specifications grading can make grading faster, clearer, and more precise, allowing the instructor to focus more on promoting improvement in students, rather than worrying about justifying a grade.

The basic tenets of specifications grading are to provide a very clear, detailed description of what is expected of the student for a given assessment (the specification), and then evaluate their submitted work as complete or incomplete against that specification—they either met the specification, or they did not. Simply providing clear expectations can make a significant difference in a student’s ability to submit what you are wanting. It almost seems too good to be true.

Historically, I have assigned points to everything students do for a course, and then determined their course grade based on the total of their earned points compared to what was possible to earn. This means that a student can do poorly on some assignments (or not do it at all), and great on other assignments, and then depend on the “extra” points from the great assignment to offset the lack of points on the poor assignment. This effectively generates an “average grade”, but does not necessarily reflect what the student accomplished. Students were also inclined to beg for partial credit.

I decided if even one of the claims Nilson made in her book title was true, it would be worthwhile implementing specs grading. My first opportunity was for a discussion-based course (CS 200: Computers and Society) during the spring 2017 semester. I converted my evaluation of all assessments to complete/incomplete—they met the detailed specifications I provided, or they did not. One exception I made to grading complete/incomplete was for the exams, although, even here, I still altered my approach. Previously I often awarded partial points for a response that contained some of the answer for which I was looking, but not all of it. For this course, I evaluated each question on a complete/incomplete basis—full points or zero. Since most of the assessments were an all or nothing situation, I did offer the students limited opportunities to resubmit incomplete assignments. In the absence of points to add up, I determined the final course grade based on how many of each assessment category the student completed. For example, if a student successfully completed at least five of six quizzes, that gave them an A, provided they had an A in all other assessment categories. If they only passed four, they dropped to a B, etcetera.

I found it critical to clearly (and repeatedly) explain to the students why I was grading this way, and what the benefits were for them and their learning. I made minor adjustments, based on my experiences and student feedback, and implemented specs grading for the same course during the summer 2017 semester as well. I have just completed the fall 2017 semester during which I implemented specs grading on two more courses. One of these courses (CS 239: Social and Professional Issues) I implemented the same way I did the CS 200 course during the spring 2017 semester. For the second course (CS 222: Advanced Programming), I used specs grading on all assessments, excepting the programming projects. For the projects, I continued to assign points based on how close to a correct solution they were. The projects were a category of assessment items, and had a different minimum points the student had to accumulate for each letter grade.

Reflecting on my experiences teaching courses utilizing specifications grading, I observed a variety of positive outcomes, including the following.
  • Students did not beg for missed points. Although there were a few (very few!) times when a student asked if I would consider passing a given assignment, rather than the failing evaluation I had provided.
  • As a whole, final course grades stayed substantially the same in the specifications-graded courses, compared to before I implemented specifications grading. I believe however, that the grades more accurately reflect the level of course content mastery. That is, if a student received a course grade of “B”, they had mastered most all of the course material at a “B” level or better, as opposed to some material at an “A” level, and other material at a “C” level.
Not all was perfect, however. My experiences and student feedback did highlight some areas that needed adjustment, including the following.
  • I needed to provide a better explanation and justification for using specifications grading at the start of the semester.
  • I did not originally provide enough detail in a few of the specifications. Others contained minor ambiguities.
  • Specification grading has not significantly reduced my grading time. In large part, this is because I want to provide the student with as much feedback as possible as soon as possible, rather than stopping my evaluation as soon as I found a specification they did not meet.
  • Some students became discouraged and gave up when they failed too many assignments.
Thus far, students tend to either like, or dislike the use of specifications grading; there is not much middle ground. Some student quotes from the end-of-semester course evaluation may serve to illustrate this. Students in the CS 222 course offered these comments about specification grading (I list the positives, and then the negatives):
“The grading system was very clear. Everyone knew what needed to be done for a specific grade.”
“Unique grading system, which might seem daunting at first, but is overall a worthwhile system.”
“Grading system is a complete mess, I know it's newish, but it really doesn't have a place in an advanced programming class.”
“Specification grading encouraged me to not complete more achievements because I knew that I could not get a grader higher than a C because of my project scores. In that regard, I think standard weighted grading systems are better as every assignment counts. In this system, students will always have incentives to work hard on every remaining assignment because they all impact the student's grade.”
The student comments in the CS 239 course were all on the negative end of the scale.
“The fact that you could have one hundred percent on everything throughout the semester, but then get a B on the final and it would bring your final grade down to a B was kind of ridiculous, especially for a one credit hour class”
“This course has a horrible grading system. Pass/Fail for sections would have been alright, if they were then averaged.”
“The grading system needs revision.”
“I hate this grading scale. People are naturally going to be better in certain areas and it seems unfair for their skill in those areas not matter if they don't do well in another area. Because of the specification grading I did only the bare minimum on all of the assignments because I knew there was less weight placed on my actual skill on that assignment.”
This course has a clear grading system.
Interestingly, if we look at the student responses to Likert scale questions that are part of the course evaluation, we get a much more positive response for both courses. The response rate for CS 222 was 20 of 39 students or 64.5%, and for CS 239 was 22 of 30 or 73.3%. The questions related to specifications grading were the following:

The use of specification grading in this course encouraged me to complete more of my work well, rather than depending on a good grade on one item to cover lesser performance on another item.

The use of specification grading in this course encouraged me to attend class regularly, since I knew it would have a direct impact on my final course grade.

I felt like I could determine my final course grade (or my path towards it) more accurately at any time during the semester because of the use of specification grading.
Once I got used to it, I wish more instructors used specification grading for their courses.
All five questions had a combined strongly agree and agree that was beyond 65%, with many of them being 80% or better. Apparently those that disliked specifications grading must have been more inclined to provide comments.