Documentation:Learning Design/LD Template

From Kumu Wiki - TRU
< Documentation:Learning Design
Revision as of 11:37, 7 May 2014 by Smauricio (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
[Goodyear] (2005) Conole (2007) Koper (2005) Oliver et al. (2007)

Organization Forms Learning Environment


Pedagogy Tasks (associative, cognitive, situative)

Learning objectives

Roles, Activities, Environment


Tasks Support mechanisms

Activity types based on Paulsen ( ) Activity types (based on Laurillard 1993):

assimilative information handling adaptive communicative productive experiential


Design rules:

Learning situation = Method based on: outcomes, environment, audience, technology supports available

Four design types:

Rule-based Incident-based Strategy-based Role-based

Template: Title (generic)

Activity type: <range type="comment" id="991134">Scaffolding, Culminating</range id="991134"> Linked activities: Interaction types: Facilitation requirements: Activity Patterns: Activity tasks/time: Sequencing: Supports (metacognitive, frameworks):

Case or Example: (postpone until we develop actual generic...this is the case for now) Learning Environment requirements: Tools Support

Learning Design Activities_data.xlsx

Template: Phylogeny

Activity type: Culminating - Activate prior knowledge and apply to new situation or problem. Linked activities: (Assimilative) - read/questions -]

Interaction types: Paired (learner-learner) Facilitation requirements: Management, Monitoring Activity Patterns <range type="comment" id="888485">(events)</range id="888485">: Identify, Analyse, Create, Compare/Contrast, Reflect

Activity tasks: 1. Identify - With a partner work together to categorize and identify 10 different "species" of candy or chocolate bar. 2. Analyse - After your initial categorization, take another look at your species and look for the characteristics that better differentiate the different types 3. Create - When you have at least fifteen characteristics, start coding your bars for each. Use your coding to create a phylogenetic tree. 4. Compare/contrast - post your phylogeny tree to your blog, and then compare/contrast yours with your peers. 5. Reflect: Do any results surprise you? Did different teams use different categories than you did? Would you go back and make any changes?

Learning Environment requirements: Asynchronous communication space Tools Support