A Comparison of Immediate and Scheduled Feedback in Introductory Programming Projects
Open accessAbstract
How students are assessed has a powerful effect on their strategies for studying and their learning. When designing assessments, instructors should consider how different approaches for providing feedback to students could encourage positive learning behaviours. One such design is the use of interim deadlines that enable students to receive and respond to feedback. This is used to encourage students to start early and thus reduce the negative effects of procrastination. If multiple submissions are allowed, penalty schemes can be included to encourage students to reflect deeply on the feedback they receive, rather than developing an over-reliance on autograders. In this work we describe two approaches to feedback used over two consecutive semesters for a final project in a large introductory programming course. In both semesters, the complexity and structure of the final project was similar and students received identical instruction. In the first instance of the course students could submit their work prior to two scheduled interim deadlines, after which they would receive automated feedback, before meeting a final third deadline. In the second instance, students received automated feedback immediately upon submission but with increasing penalties to discourage excessive submissions. In both cases, the ability to receive automated feedback -- both scheduled and immediate -- was designed to encourage early participation with the project. Under the two feedback schemes, we observed different patterns of behaviour -- particularly for the lower performing students. We explore the benefits and drawbacks of the two schemes and consider implications for future project grading.
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
The citation lists haven’t been fetched yet
References 33 · Cited by 32
Research works printed but not linked: 11
- [1]1. Kirsti M Ala-Mutka. 2005. A survey of automated assessment approaches for programming assignments. Computer science education 15, 2 (2005), 83-102.
- [2]2. Tapio Auvinen. 2015. Harmful Study Habits in Online Learning Environments with Automatic Assessment. In 2015 International Conf. on Learning and Teaching in Computing and Engineering. 50-57.
- [8]8. Rachel Cardell-Oliver. 2011. How can software metrics help novice programmers?. In Proceedings of the Thirteenth Australasian Computing Education Conf.-Volume 114. 55-62.
- [11]11. Paul Denny, Andrew Luxton-Reilly, Ewan Tempero, and Jacob Hendrickx. 2011. Codewrite: supporting student-driven practice of java. In Proceedings of the 42nd ACM technical symposium on Computer Science Education. 471-476.
- [14]14. Paul Denny, Jacqueline Whalley, and Juho Leinonen. 2021. Promoting Early Engagement with Programming Assignments Using Scheduled Automated Feed- back. In Australasian Computing Education Conf. 88-95.
- [16]16. Stephen H Edwards and Krishnan Panamalai Murali. 2017. CodeWorkout: short programming exercises with built-in data collection. In Proceedings of the 2017 ACM Conf. on Innovation and Technology in Computer Science Education. 188-193.
- [17]17. Stephen H Edwards and Manuel A Perez-Quinones. 2008. Web-CAT: automati- cally grading programming assignments. In Proceedings of the 13th annual conf. on Innovation and technology in computer science education. 328-328.
- [19]19. Tommy Färnqvist and Fredrik Heintz. 2016. Competition and feedback through automated assessment in a data structures and algorithms course. In Proceedings of the 2016 ACM Conf. on Innovation and Technology in Computer Science Education. 130-135.
- [25]25. Theresia Devi Indriasari, Andrew Luxton-Reilly, and Paul Denny. 2021. Improving Student Peer Code Review Using Gamification. In Australasian Computing Edu- cation Conference (Virtual, SA, Australia) (ACE '21). Association for Computing Machinery, New York, NY, USA, 80-87.
- [40]40. Jacqueline L Whalley and Anne Philpott. 2011. A unit testing approach to build- ing novice programmers' skills and confidence. In Proceedings of the Thirteenth Australasian Computing Education Conf., Vol. 114. 113-118.
- [41]41. Dylan Wiliam. 2011. What is assessment for learning? Studies in educational evaluation 37, 1 (2011), 3-14.
- Authors
- Leinonen, J., Denny, P., & Whalley, J.
- Affiliations
- Aalto University (FI)
- University of Auckland (NZ)
- Auckland University of Technology (NZ)
- Venue
- Proceedings of the 53rd ACM Technical Symposium on Computer Science Education
- Publisher
- ACM
- Published
- 2022-02-22
- Pages
- 885-891
- OpenAlex
- W4290460128
- Cited by
- 32
- References
- 33
- Citations by year
- 2026: 2 · 2025: 7 · 2024: 8 · 2023: 11 · 2022: 4
- FWCI
- 9.78
- Type
- conference paper
- Language
- en
- Open access
- bronze
- doi.org
- Locations
- ACM Technical Symposium on Computer Science Education (SIGCSE) (publishedVersion)
- Aaltodoc (Aalto University) (submittedVersion, other-oa)
- Funders
- Media-alan tutkimussäätiö
- Topics
- Physical Sciences › Computer Science › Computer Science Applications › Teaching and Learning Programming
- Social Sciences › Education › Student Assessment and Feedback
- Social Sciences › Education › Problem and Project Based Learning
- Keywords
- automated feedback, immediate feedback, procrastination, programming projects, penalty schemes, multiple submissions, automated grading, introductory programming, student behavior, lower-performing students
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review