WELCOME!

1. Instructor Matthew J. Koehler WELCOME! Teaching Asst Aman Yadav CEP 817: Learning Technology through Design

2. Apollo 13AKA: classmates, we have a problem • Students Count off by 4 • Faculty Count off by 4 • Get into groups by numbers • Get assignment from Matt • Come back in an hour

3. Welcome! CEP 817 • Apollo 13 • Introductions • Break • Course Overview • Homework Assignments • Faculty Sales Pitch - Low Term APR, 4 months financing, terms subject to change, other lease terms may apply, please read fine print

4. Apollo 13 - Power-points • Each group shows their powerpoint • Introduce your group • Show the presentation • No pre-amble • No talking during • Short discussion afterwords

5. Why Apollo 13? • It is the whole CEP817 compressed into one hour • Semester-long project structure is similar • An ill-defined problem • A period of panic/floundering • Some initial ideas that are kept, some modified, some discarded • People self-defining roles and responsibilities • A tight deadline (and a real one) • Cannot be completed without organization and skills (both technical and interpersonal)

6. Why Apollo 13? • It is the whole CEP817 compressed into one hour • The format is the same: Some groupwork, some whole-class time • Instructor / Student roles are the same • I’m most likely to talk to you while circulating around the room • I will never tell you what the “right answer” is. • Technology is learned as needed, by individuals (not through direct instruction from prof or TA).

7. Why Apollo 13? • It will follow the same rough chronology as the online course design • Starting with an ill-defined goal • A period of panic/floundering • Some initial ideas, some which are kept, some are modified, and some are discarded altogether • People settling into roles and responsibilities • A product is complete at the end (in the course design, there will be chances for feedback and revision)

8. Why Apollo 13? • Models the “Design Approach” • Learning is hands-on • Instructor as coach/mentor • Learn by doing • Learning in an authentic context

9. What will happen in CEP817 • We will chose groups next week - each group will be one faculty member and 3 graduate students • Handouts are being circulated for you to consider before next week • There will be some time to talk to faculty next week to help you decide. • The process is semi-voluntary

10. What will happen in CEP817 • Each week we will spend some time • As a whole group, introducing and discussing issues • Short technology demos • Most time spent in groups working, on your own, on short (e.g. getting a syllabus up) and long-term goals (designing an on-line course). • Doing readings, work, and discussions during the week outside of class

11. Course Readings • Each week there will probably be some reading • Palloff, M. & Pratt, K. (2001). Lessons from the Cyberspace Classroom: Realities of Online Teaching. Josey-Bass: San Francisco, CA.

12. What will/will not happen … • WILL NOT:Explicit instruction to train you to be HTML or web experts • WILL: You will pick up technological skills as needed, largely on your own with some help from us and your classmates • WILL NOT: Conducting or reviewing the latest research on online teaching and learning • WILL: Discuss current issues as they relate to our experiences designing the course

13. Assessment • So, how am I going to give grades for all this work? • (20%) Biweekly progress reports • (20%) Online and inclass discussion • (20%) Final Paper • (20%) Assessment of final course produced • (10%) Group Work • (10%) Facilitating an online discussion

14. Assessment • Tri-weekly progress reports • Every third week, you will submit a short progress report that contains information about what your goals are, what you've accomplished, what you're have been doing, and what you will be doing. • Online and In-class discussion • Each week, you are required to post something to the ongoing online discussion for the class. Each week will have a discussion facilitator, and your job is to contribute to that discussion. The online component (10%) is a simply a reflection, each week, of whether or not you contributed the discussion. The in class component of participation (10%) will be a subjective grade assigned by the instructor.

15. Assessment • Final Paper • There are no exams or final projects (per se) for this course. However, you do have to write one formal paper that is due on the last day we meet. This paper should be 8-10 pages long and be a reflection over the your experiences during the semester. • Project Result • A part of your grade is based upon an assessment of how well the group did. The instructor will judge how well the group did in accomplishing their goal of reaching a prototyped web site for the course under development. • Group Work • This grade is a reflection of how well you worked with your groupmates (how well you play with others). This grade will be assigned after consultation with your faculty group leader.

16. Assessment • Discussion Facilitation - • Every student will be responsible for leading and facilitating the online discussion for one week. When it is your week, it is your job to start the conversation, to set the topic, and facilitate and manage the conversation. Your job, is to explore potential ways to do this. By the end of the course, we'll have many different approaches to compare and contrast. • More detail about that in the syllabus • Sign ups will occur next week.

17. Course Website • http://blackboard.msu.edu • A short tour

18. Homework! • Blackboard • Read Syllabus on line • Do Technology Survey • Post something to discussion board • Update your profile, including picture • Read Faculty profiles • Buy Books • Look up your schedule to think of weeks when you could facilitate

19. Next week • Get into working groups • Sign up for facilitation weeks • Dreamweaver 101 • Meet the TA • Have fun

20. Faculty Speak • 2 minute introduction from each • Pick up handouts on the way out