Difference between revisions of "Nominate One Communicator"
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 10:49, 16 May 2017
| Nominate One Communicator | |
| Contributors | Christian Köppe |
|---|---|
| Last modification | May 16, 2017 |
| Source | Köppe (2012)[1] |
| Pattern formats | OPR Alexandrian |
| Usability | |
| Learning domain | |
| Stakeholders | |
Sometimes different groups have to communicate during a project or a group has to communicate with a teacher very often. If everybody communicates with everybody then there is a high chance of inefficient and vague communication, which hinders all groups in their work.
Therefore: Determine fixed communication moments and give one group member the responsibility for communicating with the other teams or the teacher.
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.