iRubric: Coding Assessment rubric

edit print share Copy to my rubrics Bookmark test run assess... delete Do more...
Coding Assessment Coding Assessment Coding is one or more commands or algorithm(s) designed to be carried out by a computer. While learning to code students are asked to follow the teacher's instructions, complete a number of tasks and persevere through problem solving. Rubric Code: G22WAB4 By cmscms Ready to use Public Rubric Subject: Computers Type: Project Grade Levels: K-5

Coding
	Poor 1 pts	Fair 3 pts	Good 5 pts
Listen to and follow instructions The student will use the given tabs and buttons to complete the desired actions on Scratch	Poor Student had a lot of trouble following instructions. Student required a lot of repetition and clarification from the teacher.	Fair Student had one or two minor difficulties, but generally followed instructions with ease. Student required a little repetition and clarification from the teacher.	Good Student had no difficulties in following instructions. Student required no repetition or clarification from the teacher.
Task completion The student will complete a number of assigned tasks on Scratch	Poor Student completed less than 10 coding tasks.	Fair Student was able to complete 11-19 coding tasks.	Good Student was able to complete more than 20 coding tasks.
Animation/Congratulation/Answer The program, when run has an animation a congratulations message or told you the correct answer	Poor The program had one of the 3 components	Fair The program has at least 2 of the components	Good The program had all 3 or more components.
Play again message TheThe program has some kind of message asking you to play again	Poor Their was no message. Program ended	Fair Their was a message but the program ended	Good Their was a message that enticed you to continue playing the game that successfully took you back to the beginning
journal Students will keep a daily journal and record what they attempted to do daily and if it was successful or not	Poor There were a few gaps due to absences only. Students kept limited records of successes or failures.	Fair There were no gaps but were days that the intro or exit entry is missing. Students kept record of only successes or failures but gave little to no explanation	Good There were no gaps or days that an intro or exit record was missed. Students kept a good written record of successes and failures and why they think they happened.