disted12

37
One Week, One Course A rapid prototyping concept for online course development Scott Schopieray College of Arts and Letters Michigan State University

Upload: schopie1

Post on 23-Jun-2015

88 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: Disted12

One Week, One Course

A rapid prototyping concept for online course development

Scott SchopierayCollege of Arts and LettersMichigan State University

Page 2: Disted12

What is OWOC?

• Brings Faculty, staff and students together for an intensive week of focused work on one course

• Opportunity to break course development down into core components

Page 3: Disted12

History of the project

Some rights reserved by derrickting

Page 4: Disted12

Initial Pilot Opportunities

• May/June 2010 – Integrated Arts/Humanities course – 50% blend

• March/April 2011 – Special topics course on German Fairy Tales – Fully Online

Both courses ATT Award winnershttp://attawards.msu.edu/

Page 5: Disted12

About OWOC

• Faculty must teach course afterward

• Faculty were given a small stipend for participation

• College/vuDAT provided resources, personnel, and lunch

• Continued support provided afterward

Page 6: Disted12

What is a Sprint?

Some rights reserved by Uninen

Page 7: Disted12

Why do sprints seem to work?

Traditional Sprint OWOC Sprint

A coach directs: suggesting tasks, tracking progress and ensuring that

no one is stuckAcademic Technology Director

Most work happens in pairs. Partners with complementary skills. Faculty paired with an eProducer

A large open space is often chosen as a venue for efficient

communication.

We used a common space (Creativity Exploratory) for everyone

to use

Project members meet in person, socialize, and start to communicate more effectively than when working

together remotely or asynchronously

Forge a relationship that carries over into remaining development

Page 8: Disted12

Timeline

• Faculty commitment (-3-5 weeks)• Pre-Meeting 1 (-2 weeks)• Pre-Meeting 2 (-1 week)• Sprint week

Page 9: Disted12

Where did we start?

• 2 Blended courses• 2 FTF courses• 1 Course idea

• 4 Faculty Members, 1 Graduate Student, 1 Visiting Faculty – 6 tech staff

Page 10: Disted12

Pre-Sprint Activities

Page 11: Disted12

Binding Contractual Commitments

• Instructors / SMEs• Project manager / General

contractor• Production Sub-contracts• Instructional Designers• Vendors / Partners

Some rights reserved by NobMouse

Page 12: Disted12

Initial Project Plan & Timeline

• Milestones for pre-sprint activities• Sprint scheduling• Time allowance for

post-sprint• Timeline for course launch• Rough-out evaluation/improvement

Some rights reserved by Cerebro Flickr

Page 13: Disted12

Big-Picture Course Design

• Lay out vision for course• Teaching style• Delivery strategy• Basic Assessment plan

Some rights reserved by London Permaculture

Page 14: Disted12

Learning Objectives

• Pre-requisite knowledge/skills• Demonstrable Knowledge• Expected

performance

Some rights reserved by Miss Lazy

Page 15: Disted12

Preparation of Lectures/Activities

• Slides / narrative / images / diagrams• Examples and activities• Outlines and storyboards• Complete initial drafts• Identify tools/resources

Page 16: Disted12

Search & Review Potential Readings

• Includes any potential readings/resources• Open Courseware• Publisher E-content & Learning Environs• Books / Articles• Library Materials• Museum Collections• Etc

Page 17: Disted12

One Week - Sprint Period

Page 18: Disted12

Facilities – Creativity Exploratory

http://ce.cal.msu.edu/

Page 19: Disted12

Production of Courseware & Lectures

• Lecture Recording• Lecture Capture• Drafting and Copywriting• Assembly of main

components• Configuration of E-learning platform• Drafting and Copywriting• Instructional Presence & Narrative

Some rights reserved by Pip R. Lagenta

Page 20: Disted12

Selection of Readings & Resources

• Final selection of assigned readings list

• Beginning of copyright clearance process

• Integration of licensed content with homegrown

• Deployment of materials in E-learning system

Some rights reserved by pindec

Page 21: Disted12

Revised Project Plan

• What's left to do?• Takeaway assignments for

SME• Distribution of tasks to

sub-contractors• Agreement on final approval process• Commitment to milestones

Page 22: Disted12

Typical Day

• 9am - Convene/Work Plan• 9:30am-Noon - Work with support• 12:00-1:30 - Lunch with guest• 1:30-3:00 - Continue work• After hours is “homework” time

* Note: We often stopped to share, ask questions, etc.

Page 23: Disted12

Post-Sprint / Pre-Offering Period

Page 24: Disted12

Complete Writing & Editing to obtain Final Copy

• Instructional design • Final writing by SME• Proofing & editing• Copywriting final E-text & narrative• Prep of pre-scripted communications

Some rights reserved by NotoriousJEN

Page 25: Disted12

Set Final Delivery Schedule

• In-line with marketing plan• Takes into account overall

production timeline

Page 26: Disted12

Copyright Clearance / Licensing

• 3rd Party materials• Selection of Open-Licensed

Alternatives• Licensing via Board of

Trustees/Administrators• University Author clearance• Etc.

Page 27: Disted12

Final Accessibility Review

• Final check against ADA/508 standards• Alternative assignments/materials• Final technical remediation

Page 28: Disted12

Post-Offering Period

Page 29: Disted12

Course Evaluation

• e.g. Quality Matters• Curricular Review (by faculty - dept)• Student Feedback• Learning Outcomes

Page 30: Disted12

Continuous Improvement/Revision

• Incremental Changes by Instructor or ID• Repeat Process• What is shelf-life of course?

Page 31: Disted12

Outcomes

• 2 web applications (timeline and gallery)http://widgets.cal.msu.edu/

• Focused work on 5 courses (range from beginning to finished)

• Collaboration among faculty and staff• Discussion about issues and tools for

online learning

Page 32: Disted12

Why Use this Method?

• Faculty typically don't have a lot of time during the school year to focus on new development

• It's difficult to train new instructional designers during the school year

• Hands-on technology workshops typically get low turnout during the school year

Page 33: Disted12

Lessons Learned

• Some preference for more of a workshop-style offering rather than work time

• Lunch was a hit – then days went longer

• Change format

• 2-3 Tech staff – collaboration key

• Create contracts and sign them!

Page 34: Disted12

Faculty Feedback (n=6)

• Overall Experience - mean 4.8/5

• Would you participate again? – mean 4.6/5

• Do you feel you were successful in reaching your goals? – mean 4.5/5

Page 35: Disted12

Faculty Feedback

• “I would do this again in a heartbeat. If fit my learning style very well and I was provided a lovely lunch every day and I got paid for my time. Excellent!”

• “Thank you so much to the IT staff that was available, patient, effective listeners, exciting brainstormers, and enjoyable to work with. Great job!”

Page 36: Disted12

Implementing at your institution

• Download the facilitator packet at:http://owoc.cal.msu.edu/

• Plan well ahead – recruit interested faculty• Meet with technology staff/other support

staff ahead of time, explain process• Provide incentives – lunch, funding, tech

toys, etc.

Page 37: Disted12

Questions?

Presentation at http://owoc.cal.msu.edu/

[email protected]