Difference between revisions of "Let the Plan Go"
Jump to navigation
Jump to search
Sfrancisco (talk | contribs) (Added contributors) |
Sfrancisco (talk | contribs) (Added category) |
||
| Line 65: | Line 65: | ||
<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:03, 4 May 2017
| Let the Plan Go | |
| Contributors | Astrid Fricke, Markus Völter |
|---|---|
| Last modification | May 4, 2017 |
| Source | Fricke and Völter (2000)[1] |
| Pattern formats | OPR Alexandrian |
| Usability | |
| Learning domain | |
| Stakeholders | |
If a question arises that you haven’t expected in your planning, but answering it would add nicely to your lecture, then take the time for this sidestep[1].
Context
Problem
Forces
Solution
Consequences
Benefits
Liabilities
Evidence
Literature
Discussion
Data
Applied evaluation
Related patterns
This requires that you have included Buffers in your planning.
Example
References
- ↑ 1.0 1.1 Fricke, A., & Völter, M. (2000). SEMINARS: A Pedagogical Pattern Language about teaching seminars effectively. In Proceedings of the 5th European Conference on Pattern Languages of Programs, EuroPLoP 2000 (pp. 87-128). New York:ACM.