Difference between revisions of "Resolve Conflicts"
Jump to navigation
Jump to search
***
Sfrancisco (talk | contribs) (Added category) |
Sfrancisco (talk | contribs) (Added category) |
||
| 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 11:38, 16 May 2017
| Resolve Conflicts | |
| Contributors | Christian Köppe |
|---|---|
| Last modification | May 16, 2017 |
| Source | Köppe (2012)[1] |
| Pattern formats | OPR Alexandrian |
| Usability | |
| Learning domain | |
| Stakeholders | |
There is a clash between group members, which has negative impact on the motivation and participation.
Therefore: Identify the cause of the clash together with the concerned group members — and maybe some outside person like the teacher — and look for a solution where both parties can live with.
Context
Problem
Forces
Solution
Consequences
Benefits
Liabilities
Evidence
Literature
Discussion
Data
Applied evaluation
Related patterns
Example
References
- ↑ 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.