Difference between pages "Reflect on Learning from Failure (Framework)" and "Course Materials Sprint 2018"

From TeachingOpenSource
(Difference between pages)
 
m (1 revision imported)
 
Line 1: Line 1:
__NOTOC__
__NOTOC__


{{Learning Activity Overview
== Course Materials Sprint ==
|title=
=== Nassau Community College ===
Reflect on Learning from Failure (Framework)
=== June 3-5, 2018 ===
|overview=  
'''Overview:''' The overall goal of this project is to make a group of complete courses available to other faculty. This course sprint is part of that effort, and our intention is to emphasize activities that are more difficult to achieve when we are working individually.
We want students to understand how much they learn from their failures during the course instead of getting frustrated over it.
|prerequisites=
This framework can potentially be integrated for any of the courses using FOSS continuously.
|objectives=
Reflect on their progress in a project or course.
|process skills=
[[:Category:Assessment|Assessment]]
}}


== Background ==
'''Goals:'''
# Review, critique, and improve syllabi for each course with particular focus on learning outcomes, course topics, and approach to learning
# Review, critique and improve selected materials from each course (lectures, learning activities, assessments, etc)
# Review and improve structure for packaging and disseminating each course
# Review and improve approaches to learning evaluation
# Discuss potential for publication of results across institutions


=== Rationale ===
'''Pre-work:'''
# Provide basic information about your course so that we can see how the set of courses relate to each other.  You can do this by completing the template [https://docs.google.com/document/d/17kd8n3Ocerj1UhWdlS8h4tKlOMpcQRA5xUWHwHZ0t_Y/edit here]
# Make syllabus and materials available - We would like to have shared access to the current version of everyone’s course.  We’ll figure out the best platform for that once we have the basic information about all the courses requested above.
# Be prepared to provide a 25-30 minute guided tour of your course. Please include:
## What went well
## What you would change
## Lessons learned
# Have at least a draft syllabus
# Bring with you a brief overview of 2-3 key learning activities for course
## Provide one that works well and one or two that need improvement or need to be developed
## These could be materials already developed or activities that are needed
## Those who are still developing courses can present 2-3 activities that need to be developed


Our framework is motivated by the following:
== Agenda ==
* Students will get critiqued in the world they'll enter into. They need to learn how to deal with that in a constructive way.
* Students often presume others are doing better than them.
* Students associate being “productively lost” with failure.
* Underrepresented groups in CS can be challenged by a lack of confidence (including, but not limited to issues of stereotype threat).


=== Readings===
* Barker, Lecia J., Charlie McDowell, and Kimberly Kalahar. "Exploring factors that influence computer science introductory course students to persist in the major." ACM SIGCSE Bulletin. Vol. 41. No. 1. ACM, 2009.
* Dryburgh, Heather. "Underrepresentation of girls and women in computer science: Classification of 1990s research." Journal of Educational Computing Research 23.2 (2000): 181-202.
* Margolis, Jane, and Allan Fisher. Unlocking the clubhouse: Women in computing. MIT press, 2003 | https://pdfs.semanticscholar.org/c814/d8d066e64095e03d3193786b2fdd15243cac.pdf
* Roger Von Oech - A Whack on the Side of the Head: How You Can Be More Creative - http://courses.washington.edu/art166sp/documents/Spring2012/readings/week_3/AWhackOnTheSideOfTheHead.pdf
== Directions & deliverables ==
=== Micro-reflections ===
''Extremely short "Tweet-sized", scheduled, in-class reflections asking the student to step out of their current activity, think about their current mindset, then return to the activity.''
* Regular interval during class, e.g. every 30 minutes in class
* There is a social aspect to sharing them as tangible artifacts that help students step out of the technical details to see the social skills for a moment. Color-coded notes/notecards could be used for various categories (technical, communication, big picture, etc.)
* Some ways to think about implementing micro-reflections:
** Commit messages where students state their current stage of thought/problem-solving process, snapshot of where they’re at. If collecting them in a different place is preferred, a shared doc is an option.
** Index cards / Post-its if computers aren’t in use (and public, can optionally be categorized), but would have to be written up / redistributed / photographed if they are supposed to be available to the students for macro reflections.
=== Mini-reflections ===
''(weekly; outside of class) - longer reflections (e.g., 2-3 paragraphs) with prompted topics.''
* Some ways to think about implementing mini-reflections:
** Summarization of micro-reflections
** Blog
** Wiki
* Prompt a different category every week: soft skills, technical aspect, communication, organization
=== Final/macro/meta Reflections ===
''(1-3 at milestones/checkpoints; outside of class) - Summative reflection, asking the students to re-explore their process from a previous period/project.''
* Suggested milestones: start of the semester (survey), middle of semester (survey), end of semester (survey and essay)
*Some ways to think about implementing Final/macro/meta Reflections (more than one may be appropriate):
** Surveys: use existing FOSS surveys and maybe add a couple of questions
** Short essay with reflection at the end (using their micro reflections) and the prompt to reflect on how they learned from failure.
=== ''Progress visualization over an academic term...'' ===
* How can we (help students) visualize progress? Charting on the following fronts:
* Let students set a goal - may be unrealistic but they engage more if they can contribute creatively
* Level of frustration, just for giggles, hoping it goes down over the semester ;)
* Learning goals / objectives (for the course, as determined by instructor)
* Data collection via Moodle/BlackBoard/whatever your course is already using
= Notes for Instructors =
The remaining sections of this document are intended for the instructor.  They are not part of the learning activity that would be given to students.
=== Assessment ===
'''How will the activity be graded?''' The larger the reflection, the more weight it gets assigned.
* The micro reflections are not graded on content, just on process (which basically means whether students did them or not).
* The mini reflections can be graded using questions below.
* The macro reflection can be graded using same and further questions.
* The data tracking is graded on process - did they submit their numbers or not.
How will learning will be measured? Ideally, there should be a way to measure each of the objectives described above.
How will feedback to the student be determined?
Include sample assessment questions/rubrics. Feel free to indicate that the activity itself is not graded, however it would be helpful to include any questions that might be used at a later date to interpret learning, for example on a quiz or exam.
The form of the assessment is expected to vary by assignment. One possible format is the table:
{| class="wikitable"
{| class="wikitable"
! Criteria
! Time
! Level 1 (fail)
! Activity
! Level 2 (pass)
! Level 3 (good)
! Level 4 (exceptional)
|-
|-
| '''How well did they follow the prompt on what to write about? '''
| X
|
|
|
! Monday, June 4, 2018
|-
| 8:45 AM
| Arrive at Nassau Community College - building CCB, room 210
|-
| 9:00 AM
| Introductions/Orientation
|-
| 9:30 AM
| Introduction to Existing Courses
* Brief overview by those who have run or are developing a course
* Presentation of syllabi
* Discussion of learning materials selection
* Observations on the course
|-
| 10:30 AM
| Break
|-
| 10:45
| Introduction to Existing Courses - cont.
|-
| 12:00 NOON
| Lunch
|-
| 1:00 PM
| Brief overview of 2-3 key learning activities for course
* Provide one that works well and one or two that need improvement or need to be developed
* These could be materials already developed or activities that are needed
* Those who are still developing courses can present 2-3 activities that need to be developed
|-
| 1:45 PM
| In pairs or threes critique and/or develop materials identified above
|-
| 3:00 PM
| Report out
|-
| 3:15 PM
| Break
|-
| 3:30 PM
| Decide on dissemination approach
* Presentation of proposed structure (Greg/Heidi)
* Review current structure for courses on TeachingOpenSource and foss2serve
* Discussion/revision
|-
| 4:30 PM
| Evaluation Plan and Tools - review and update
* Materials Review (rest of afternoon)
* Discuss publication options
* Wrap-up and planning for day 2
|-
| 6:00 PM
| Dinner ordered in
|-
|
|
 
! Tuesday, June 5, 2018
|-
| ?
| Breakfast on your own
|-
| 9:00 AM
| Packaging and Dissemination Discussion
|-
| 10:30 AM
| Break
|-
| 10:45 AM
| Packaging and Dissemination Discussion/Implementation
* Assessment
|-
| 12:00 NOON
| Lunch - Discuss what sort of support would be helpful during the course - how can TOS community help?
|-
| 1:00 PM
| Continue disucssion
|-
| 2:00 PM
| Plan steps going forward
|-
|-
| '''Did they describe their observations well?'''
| 3:00 PM
| X
| Wrap Up
| X
|
|
 
|-
|-
| '''Did they draw conclusions from their observations?'''
| 3:30 PM
| X
| Adjourn
| X
|}
| X
|  


|-
| '''Did they conclude lessons learned?'''
| X
| X
| X
| X


|}


=== Comments ===
=== Resources ===


What should the instructor know before using this activity?
Here is a link to the course I have been presenting/revising this Summer. I will definitely be presenting this again in Summer 2019 to an anticipated class of 30-40 students and may be presenting it as well in Spring 2019 depending on student demand.
==== Note: ====
This is a first run-through and I will be continuing to revise it and extend it both this Summer and over the next few months. I will also be adding issues to the issue tracker on what needs to change over the next few semesters.


What are some likely difficulties that an instructor may encounter using this activity?
[https://github.com/rcos/CSCI-4961-01-Summer-2018 Open Source Course as taught Summer 2019 at Rensselaer Polytechnic Institute]


{{Learning Activity Info
--[[User:Wturner|Wturner]] 17:31, 24 July 2018 (UTC)
|acm unit=
|acm topic=
Soft skills: Reflection (not in ACM but it's the topic)
|difficulty=
Carrying out the writing tasks is easy, doing a good reflection is medium.
|time=
Micro: 30 seconds, Mini: 10-30 minutes, Macro: 2 hours
|environment=
Internet access if done on blog.
|author=
Birgit Penzenstadler, Emily Lovell, Mario Nakazawa, Scott Heggen, Matt Jadud
|source=
|license=
{{License CC BY SA}}
}}


=== Suggestions for Open Source Community ===


This framework seems to be more about reflection in any course context where students can fail than specifically OSS. We are not sure what suggestions may arise from that for the open source community.
* Put links to resources here


[[Category:Learning Activity]]
[[Category:Events]]
[[Category:Learning Frameworks]]
[[Category:Workshops]]
[[Category: Ready to Use]]

Latest revision as of 16:57, 13 November 2021


Course Materials Sprint

Nassau Community College

June 3-5, 2018

Overview: The overall goal of this project is to make a group of complete courses available to other faculty. This course sprint is part of that effort, and our intention is to emphasize activities that are more difficult to achieve when we are working individually.

Goals:

  1. Review, critique, and improve syllabi for each course with particular focus on learning outcomes, course topics, and approach to learning
  2. Review, critique and improve selected materials from each course (lectures, learning activities, assessments, etc)
  3. Review and improve structure for packaging and disseminating each course
  4. Review and improve approaches to learning evaluation
  5. Discuss potential for publication of results across institutions

Pre-work:

  1. Provide basic information about your course so that we can see how the set of courses relate to each other. You can do this by completing the template here
  2. Make syllabus and materials available - We would like to have shared access to the current version of everyone’s course. We’ll figure out the best platform for that once we have the basic information about all the courses requested above.
  3. Be prepared to provide a 25-30 minute guided tour of your course. Please include:
    1. What went well
    2. What you would change
    3. Lessons learned
  4. Have at least a draft syllabus
  5. Bring with you a brief overview of 2-3 key learning activities for course
    1. Provide one that works well and one or two that need improvement or need to be developed
    2. These could be materials already developed or activities that are needed
    3. Those who are still developing courses can present 2-3 activities that need to be developed

Agenda

Time Activity
Monday, June 4, 2018
8:45 AM Arrive at Nassau Community College - building CCB, room 210
9:00 AM Introductions/Orientation
9:30 AM Introduction to Existing Courses
  • Brief overview by those who have run or are developing a course
  • Presentation of syllabi
  • Discussion of learning materials selection
  • Observations on the course
10:30 AM Break
10:45 Introduction to Existing Courses - cont.
12:00 NOON Lunch
1:00 PM Brief overview of 2-3 key learning activities for course
  • Provide one that works well and one or two that need improvement or need to be developed
  • These could be materials already developed or activities that are needed
  • Those who are still developing courses can present 2-3 activities that need to be developed
1:45 PM In pairs or threes critique and/or develop materials identified above
3:00 PM Report out
3:15 PM Break
3:30 PM Decide on dissemination approach
  • Presentation of proposed structure (Greg/Heidi)
  • Review current structure for courses on TeachingOpenSource and foss2serve
  • Discussion/revision
4:30 PM Evaluation Plan and Tools - review and update
  • Materials Review (rest of afternoon)
  • Discuss publication options
  • Wrap-up and planning for day 2
6:00 PM Dinner ordered in
Tuesday, June 5, 2018
? Breakfast on your own
9:00 AM Packaging and Dissemination Discussion
10:30 AM Break
10:45 AM Packaging and Dissemination Discussion/Implementation
  • Assessment
12:00 NOON Lunch - Discuss what sort of support would be helpful during the course - how can TOS community help?
1:00 PM Continue disucssion
2:00 PM Plan steps going forward
3:00 PM Wrap Up
3:30 PM Adjourn


Resources

Here is a link to the course I have been presenting/revising this Summer. I will definitely be presenting this again in Summer 2019 to an anticipated class of 30-40 students and may be presenting it as well in Spring 2019 depending on student demand.

Note:

This is a first run-through and I will be continuing to revise it and extend it both this Summer and over the next few months. I will also be adding issues to the issue tracker on what needs to change over the next few semesters.

Open Source Course as taught Summer 2019 at Rensselaer Polytechnic Institute

--Wturner 17:31, 24 July 2018 (UTC)


  • Put links to resources here