Anonymize Solutions
Revision as of 10:59, 23 September 2016 by Sfrancisco (talk | contribs) (Created patlet for pattern)
| Anonymize Solutions | |
| Contributors | |
|---|---|
| Last modification | September 23, 2016 |
| Source | Köppe, Niels, Holwerda, Tijsma, Van Diepen, Van Turnhout, and Bakker (in press 2015)[1][2] |
| Pattern formats | OPR Alexandrian |
| Usability | |
| Learning domain | |
| Stakeholders | |
If you use bad student solutions during in-class meetings for discussing their shortcomings, then initially anonymize them, so that the students won’t be embarrassed and the focus is on the solution only.[1][2]
Context
Problem
Forces
Solution
Consequences
Benefits
Liabilities
Evidence
Literature
Discussion
Data
Applied evaluation
Related patterns
Example
References
- ↑ 1.0 1.1 First mentioned in Köppe, C., Niels, R., Holwerda, R., Tijsma, L., van Diepen, N., van Turnhout, K., Bakker, R., (2015). Flipped Classroom Patterns - Designing Valuable In-Class Meetings. In Proceedings of the 20th European Conference on Pattern Languages of Programs (EuroPLoP 2015). New York:ACM.
- ↑ 2.0 2.1 Köppe, C., Niels, R., Holwerda, R., Tijsma, L., Van Diepen, N., Van Turnhout, K., & Bakker, R. (in press 2015). Flipped Classroom Patterns - Using Student Solutions. In Proceedings of the 22nd Conference on Pattern Languages of Programs (PLoP 2015). Pittsburgh, USA.