-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Create 030-formative-assessments-learning
First creation
- Loading branch information
Showing
1 changed file
with
53 additions
and
0 deletions.
There are no files selected for viewing
53 changes: 53 additions & 0 deletions
53
_chapters/800-Incubator/030-formative-assessments-learning
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,53 @@ | ||
--- | ||
title: Formative Assessments are for Learning | ||
slug: formative-assessments-open | ||
--- | ||
## Intent | ||
|
||
Formative assessments are for learning and students should not be punished for getting things wrong while learning. | ||
|
||
## Problem | ||
|
||
Students take courses with varying degrees of prior experience. Those who have learned a subject previously are better equipped to succeed on weekly assignments in a course. Those who are brand new to a subject are still learning how to put the pieces together and are more likely to make mistakes as they learn material. Formative assessments should be an opportunity for students to interact with new material and explore how everything fits together. Making mistakes or failing to comprehend the complexity of a subject are common situations and students should not be penalized for these situations as the advance towards proficiency. Unfortunately, traditional grading models frequently grade weekly work based on overall correctness which can be penalizing for students who are making legitimate progress but have not yet progressed to significant proficiency. | ||
|
||
|
||
## Solution | ||
|
||
Examples of formative assessments could include weekly labs, weekly quizzes, practice programs, and even certain exams. | ||
Formative assessments can be repeated until students get them “right.” This may involve setting initial, recommended deadlines but allowing students to continue to work on assessments until the end of the semester. Assignments can be submitted for an initial assessment and may have conditions in place before a redo/retake attempt is allowed. However, all are understood to be for learning purposes and thus should be open for opportunities to further student learning by revisiting mistakes or improving progress. | ||
## Applicability | ||
|
||
Every play involves tradeoffs, and this is the spot to describe them and explain when this play is a good idea or works, and when it might not be applicable or might be harder to use. Answer the question of: “In what contexts should we use this play?” | ||
|
||
## How to Implement | ||
|
||
Time management, by the instructor / course staff and the students, plays a major role in the success, or failure, of this particular play. Here are some factors that implementers should consider in that regard: | ||
|
||
+ **Student procrastination**. Student assessment attempts are not uniformly distributed across the semester; students tend to put off assessments until the end of the course, and / or generally not space out assessment attempts. In the source article, the author spent an _average_ of 10 hours of week outside of class on assessments, with light weeks at the start of the term and many hours spent in the last week of the term. Instructors may want to consider ways to either incentivize students to spread out their attempts throughout the term, or to place a tight upper bound on the time spent per week on assessments. For instance, the source author limited student assessment attempts to one per day, as one way to manage instructor time and energy. | ||
+ **Instructor time allocation**. While this play requires a significant amount of time for meeting with students, for assessments and for regular office hours, some of that time does come from the time that would otherwise be devoted to grading, and managing grading. Implementers may also want to think about how and when to allow assessments: during general office hours, during specific assessment hours, during lab or class time, etc. | ||
|
||
## See Also | ||
|
||
Weighting Formative vs. Summative Assessment | ||
|
||
## Source | ||
|
||
Source: Albert Lionelle, Sudipto Ghosh, Marcia Moraes, Tran Winick, and Lindsey Nielsen. 2023. A Flexible Formative/Summative Grading System for Large Courses. In Proceedings of the 54th ACM Technical Symposium on Computer Science Education V. 1 (SIGCSE 2023). Association for Computing Machinery, New York, NY, USA, 624–630. https://doi.org/10.1145/3545945.3569810 | ||
Described by: Ben Schafer ([email protected]) | ||
|
||
## References | ||
|
||
_Insert references to publications or web pages describing, evaluating, or | ||
sharing experiences with this technique. Then remove this text._ | ||
|
||
|
||
## Community Discussion | ||
|
||
Community members are free to comment on, ask questions about, share | ||
experiences, or otherwise contribute to knowledge about this play by | ||
posting comments below. | ||
See {% include chapter-link.html slug="join-discussions" %} for details. | ||
|
||
* Insert a comment here. | ||
|
||
|