Difference between revisions of "Keep Team Spirit"
Jump to navigation
Jump to search
***
Sfrancisco (talk | contribs) (Added contributors) |
Sfrancisco (talk | contribs) (Added category) |
||
| Line 20: | Line 20: | ||
Therefore: Don’t work too long and make regularly breaks. Finish the assignment together as group with something nice you can look forward to, like going out for a beer. | Therefore: Don’t work too long and make regularly breaks. Finish the assignment together as group with something nice you can look forward to, like going out for a beer. | ||
==Context== | |||
<!-- Context of the design pattern --> | |||
==Problem== | |||
<!-- Problem the design pattern solves --> | |||
==Forces== | |||
<!-- List of forces affecting the solution. Each entry is preceded by an * For example: | |||
# Entry 1 | |||
# Entry 2 --> | |||
==Solution== | |||
<!-- Solution to the design problem --> | |||
==Consequences== | |||
===Benefits=== | |||
<!-- List of benefits from applying the solution to the problem Each entry is preceded by an * For example: | |||
# Entry 1 | |||
# Entry 2 --> | |||
===Liabilities=== | |||
<!-- List of liabilities from applying the solution to the problem Each entry is preceded by an * For example: | |||
# Entry 1 | |||
# Entry 2 --> | |||
==Evidence== | |||
===Literature=== | |||
<!-- Evidence from literature that was used in producing the pattern or evaluating the pattern--> | |||
===Discussion=== | |||
<!-- Discussion with experts or stakeholders used in producing the pattern --> | |||
===Data=== | |||
<!-- Evidence from data that was used in producing the pattern --> | |||
===Applied evaluation=== | |||
<!-- Results from randomized controlled trials (RCTs) or similar tests that measures the pattern's effectiveness in an actual application. For example, compare student learning gains in an online learning system with and without applying the pattern. --> | |||
==Related patterns== | |||
<!-- Other design patterns related to the current design pattern and a description of how it is related --> | |||
==References== | ==References== | ||
<references/> | <references/> | ||
[[Category:Design_patterns]] <!-- 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]]<!-- List of other categories the design pattern belongs to. The syntax for linking to a category is: [[Category:<Name of category]] --> | ||
Revision as of 14:35, 4 May 2017
| Keep Team Spirit | |
| Contributors | Christian Köppe |
|---|---|
| Last modification | May 4, 2017 |
| Source | Köppe (2012)[1] |
| Pattern formats | OPR Alexandrian |
| Usability | |
| Learning domain | |
| Stakeholders | |
The end of the assignment is in sight, but the motivation and inspiration starts to decrease.
Therefore: Don’t work too long and make regularly breaks. Finish the assignment together as group with something nice you can look forward to, like going out for a beer.
Context
Problem
Forces
Solution
Consequences
Benefits
Liabilities
Evidence
Literature
Discussion
Data
Applied evaluation
Related patterns
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.