Difference between revisions of "Eliminate Bottlenecks"

From Open Pattern Repository for Online Learning Systems
Jump to navigation Jump to search
(Created patlet for pattern)
 
(Added category)
 
(3 intermediate revisions by the same user not shown)
Line 4: Line 4:
{{Infobox_designpattern
{{Infobox_designpattern
|image= <!-- Provide the filename of the image to be displayed (e.g., Design_pattern.png) -->
|image= <!-- Provide the filename of the image to be displayed (e.g., Design_pattern.png) -->
|contributor= <!-- List of contributors separated by a " , "comma. This is optional so you can remove this field if there are no contributors -->
|contributor= [[Christian Köppe]]
|source= Köppe (2012)<ref name="Koppe2012">Köppe, C. (2012). [http://dl.acm.org/citation.cfm?id=2831272 Learning patterns for group assignments: part 1.] In Proceedings of the 19th Conference on Pattern Languages of Programs (PLoP 2012). The Hillside Group.</ref>
|source= Köppe (2012)<ref name="Koppe2012">Köppe, C. (2012). [http://dl.acm.org/citation.cfm?id=2831272 Learning patterns for group assignments: part 1.] In ''Proceedings of the 19th Conference on Pattern Languages of Programs (PLoP 2012)''. The Hillside Group.</ref>
|dataanalysis= <!-- If applicable, list of data analyses used for mining the pattern separated by a " , "comma -->
|dataanalysis= <!-- If applicable, list of data analyses used for mining the pattern separated by a " , "comma -->
|domain= <!-- Learning domain the design pattern belongs to (e.g., General, Math, Algebra) -->
|domain= <!-- Learning domain the design pattern belongs to (e.g., General, Math, Algebra) -->
Line 20: Line 20:
Therefore: Reassign the tasks so that everyone in the group can work and that the project is progressing smoothly.
Therefore: Reassign the tasks so that everyone in the group can work and that the project is progressing smoothly.


==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 -->
==Example==
<!-- Example of applying the design pattern -->


==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]] [[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

  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.