Reflect on Learning from Failure (Framework)

From Foss2Serve
(Difference between revisions)
Jump to: navigation, search
 
(48 intermediate revisions by 6 users not shown)
Line 1: Line 1:
Idea:
+
__NOTOC__
Describe framework and then use a concrete activity to apply our ideas for reflection on learning from failure, probably version control and issue tracking activities, which are already defined, and extending them for our perspective.
+
Rationale for our framework:
+
  
 +
{{Learning Activity Overview
 +
|title=
 +
Reflect on Learning from Failure (Framework)
 +
|overview=
 +
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]]
 +
}}
  
Students will get critiqued in the world they'll enter into. They need to learn how to deal with that in a constructive way.
+
== Background ==
Go look at someone else's code - can you understand it? If yes, students will start feeling more confident. Also, it reinforces how important code documentation is.
+
Model behavior for students in the classroom and have students suggest what to put in there, then discuss them. How can that be scaffolded?
+
Here’s some code that’s not working, do a quick quiz in class and let them find out why. Then put up “this is what most people think why it doesn’t work. Now go try fix it.”
+
  
 +
=== Rationale ===
  
Outcomes / deliverables (students’):  
+
Our framework is motivated by the following:
Micro-reflections (throughout an activity; in class)
+
* Students will get critiqued in the world they'll enter into. They need to learn how to deal with that in a constructive way.
Can be done at regular interval (e.g. every 30 minutes in class)
+
* Students often presume others are doing better than them.  
Commit messages where students state their current stage of thought/problem-solving process, snapshot of where they’re at.
+
* Students associate being “productively lost” with failure.
If collecting them in a different place is preferred, a shared doc is an option.
+
* Underrepresented groups in CS can be challenged by a lack of confidence (including, but not limited to issues of stereotype threat).
Index card / 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.
+
There is a social aspect to sharing them as tangible artifacts help students to relate and see the social skills for a moment instead of the technology. Color coded notes/notecards could be used for various categories (technical, communication, big picture, etc.)
+
Mini-reflections (weekly; outside of class):
+
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):
+
Milestones: start of the semester (survey), middle of semester (survey), end of semester (survey and essay)
+
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
+
  
 +
=== Readings===
  
→ put this on http://foss2serve.org/index.php/Framework_Reflection_on_Learning_from_Failure
+
* 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.
Background:
+
* Dryburgh, Heather. "Underrepresentation of girls and women in computer science: Classification of 1990s research." Journal of Educational Computing Research 23.2 (2000): 181-202.
Readings:
+
* 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
+
* 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"
 +
! Criteria
 +
! Level 1 (fail)
 +
! Level 2 (pass)
 +
! Level 3 (good)
 +
! Level 4 (exceptional)
 +
|-
 +
| '''How well did they follow the prompt on what to write about? '''
 +
| X
 +
|
 +
|
 +
|
 +
 
 +
|-
 +
| '''Did they describe their observations well?'''
 +
| X
 +
| X
 +
|
 +
|
 +
 
 +
|-
 +
| '''Did they draw conclusions from their observations?'''
 +
| X
 +
| X
 +
| X
 +
|
 +
 
 +
|-
 +
| '''Did they conclude lessons learned?'''
 +
| X
 +
| X
 +
| X
 +
| X
 +
 
 +
|}
 +
 
 +
=== Comments ===
 +
 
 +
What should the instructor know before using this activity?
 +
 
 +
What are some likely difficulties that an instructor may encounter using this activity?
 +
 
 +
{{Learning Activity Info
 +
|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.
 +
 
 +
[[Category:Learning Activity]]
 +
[[Category:Learning Frameworks]]
 +
[[Category: Ready to Use]]

Latest revision as of 17:37, 8 March 2017


Title

Reflect on Learning from Failure (Framework)

Overview

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.

Learning Objectives After successfully completing this activity, the learner should be able to:

Reflect on their progress in a project or course.

Process Skills Practiced

Assessment


Background

Rationale

Our framework is motivated by the following:

  • 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

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:

Criteria Level 1 (fail) Level 2 (pass) Level 3 (good) Level 4 (exceptional)
How well did they follow the prompt on what to write about? X
Did they describe their observations well? X X
Did they draw conclusions from their observations? X X X
Did they conclude lessons learned? X X X X

Comments

What should the instructor know before using this activity?

What are some likely difficulties that an instructor may encounter using this activity?

ACM Body of Knowledge
Area & Unit(s)
ACM Topic(s)

Soft skills: Reflection (not in ACM but it's the topic)

Level of Difficulty

Carrying out the writing tasks is easy, doing a good reflection is medium.

Estimated Completion Time

Micro: 30 seconds, Mini: 10-30 minutes, Macro: 2 hours

Environment / Materials

Internet access if done on blog.

Author(s)

Birgit Penzenstadler, Emily Lovell, Mario Nakazawa, Scott Heggen, Matt Jadud

Source
License

This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License

CC license.png


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.

Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox