Design Patterns for CS Education/Design Patterns/Peer critique

From Wikibooks, open books for an open world
Jump to navigation Jump to search

Peer critique

[edit | edit source]
Pattern Name

Peer Critique

Problem: Students don't know how to critique their own work.

Level (any)

Semester (any)

Activity type (any)

Solution: After one group of students present their work, other students critique. Students then critique their own critique.

The student that wrote the critique also writes an assessment of critique (what did they get out of it). Formation (random,prescribed)

Size (pairs, small)

Composition (any)

Duration (single class, topic based, project based)

Contribution to grade (small)

Activity progression (group to individual, individual to group )

Roles (equal responsibility)

Rationale: Critique is an important part of learning and it is easier to critique someone else's work before you learn to critique your own.
Potential Pitfalls: Students may produce poor critiques.