Difference between revisions of "Eliminate Bottlenecks"
Jump to navigation
Jump to search
***
Sfrancisco (talk | contribs) m (Edited format) |
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:42, 15 May 2017
| Eliminate Bottlenecks | |
| Contributors | Christian Köppe |
|---|---|
| Last modification | May 15, 2017 |
| Source | Köppe (2012)[1] |
| Pattern formats | OPR Alexandrian |
| Usability | |
| Learning domain | |
| Stakeholders | |
An assigned task is too big or too complex for the assigned members, they are not able to finish it on time and/or in sufficient quality.
Therefore: Reassign the tasks so that everyone in the group can work and that the project is progressing smoothly.
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.