June 4 Call

1 pm Pacific | 2 pm Mountain | 3 pm Central | 4 pm Eastern

There are two steps for joining the call; we will be using Adobe Connect to screenshare and an Accuconference line for audio.
Step 1: To join Adobe Connect for screensharing, please visit:

http://serc.adobeconnect.com/itg-author/(you can enter as a guest and just enter your name)

Step 2: We will be using a separate conference call line for audio:
1.800.704.9804

(or non-toll-free: 1.404.920.6604)
Access code: 872 12 952
You can also use Skype and its dial pad to call into the conference line. If you have difficulties with the toll-free number provided above, the non-toll-free option is:404.920.6604 (same access code).

Agenda:

This meeting is about making our job of supporting materials development teams to successful completion of materials easier.

First 30 minutes : Ensure we understand and agree to expectations and process for teams and that documentation supports us in ensuring that teams understand this as we do.

• finalize the contract letter, process as encoded in the timeline.
• Timeline
• contract letter Draft Contract Letter (Microsoft Word 543kB May31 13)
• discuss the documentation -- its accuracy, accessibility, and completeness
• [link /integrate/info_team_members/currdev/index.html 'Info for Materials Developers

Next 25 minutes: How we support teams

My guess is that this will be a meandering conversation that will in aggregate cover these points:

• discuss lessons learned last year as documented on this page
• discuss role of assessment consultant, webteam support and team lead and communications among these support people
• put in place a plan for supporting authors with monthly meetings addressing pedagogy, assessment, team management etc.
• role of Josh Caukins
• how to help teams learn to manage themselves well
• support on the pathway to check point one

Last 5 minutes: Understand how we are going to complete the unfinished parts of the process -- in particular case studies and module front pages and a common look/feel for modules. What can we say to module authors at this point.