Difference between revisions of "Clear Up Questions"
Jump to navigation
Jump to search
***
Sfrancisco (talk | contribs) m (Edited format) |
Sfrancisco (talk | contribs) (Added contributors) |
||
Line 69: | Line 69: | ||
<references/> | <references/> | ||
[[Category:Design_patterns]] [[Category:Patlet]]<!-- List of other categories the design pattern belongs to. The syntax for linking to a category is: [[Category:<Name of category]] --> | [[Category:Design_patterns]] [[Category:Patlet]] [[Category:Learning Patterns for Group Assignments]] [[Category:Traditional Classroom]]<!-- List of other categories the design pattern belongs to. The syntax for linking to a category is: [[Category:<Name of category]] --> |
Latest revision as of 07:51, 15 May 2017
Clear Up Questions | |
Contributors | Christian Köppe |
---|---|
Last modification | May 15, 2017 |
Source | Köppe (2012)[1][2] |
Pattern formats | OPR Alexandrian |
Usability | |
Learning domain | |
Stakeholders |
Some — or all — parts of the assignment description are vague and not understandable. Starting the assignment under these circumstances can lead to a wrong start of the work and also lead to time loss if things are done the wrong way.
Therefore: After the assignment is given, summarize what is clear about the assignment and try to identify what is not. Check this with all team members. If parts stay — or become — unclear, ask the teacher for clarification.[1][2]
Context
Problem
Forces
Solution
Consequences
Benefits
Liabilities
Evidence
Literature
Discussion
Data
Applied evaluation
Related patterns
Example
References
- ↑ 1.0 1.1 Köppe, C. (2012). Learning patterns for group assignments: part 1. In Proceedings of the 19th Conference on Pattern Languages of Programs (PLoP 2012). The Hillside Group.
- ↑ 2.0 2.1 Also mentioned in de Cortie, T., van Broeckhuijsen, R., Bosma, G., & Köppe, C. (2013). Learning patterns for group assignments: part 2. In Proceedings of the 20th Conference on Pattern Languages of Programs (PLoP 2013). The Hillside Group.