Flyout Menu

LXD Style Guide

iPD’s Guide for Course Design & Development

Google File Management

Standard

The standard with which Michigan Virtual courses need to comply. 

Current iPD project files exist in their project folder, housed within iPD Project > Current Projects for the duration of the work. Naming Convention: “SLS – Course Name “, “MVLRI – Course Name”, or “PLS – Course Name”.

The CDM will archive the folder by moving it within iPD Projects > FY xx Completed Projects during Deploy.

Requirements 

What exactly do course developers need to include in order to comply with this standard? 

All assets must be obtained and uploaded into the Google project folder from the SME, ID, CDA, and any other project members throughout the duration of the project. All assets should be accounted for during “Deploy”. This includes:

  • Communications including Project Requirements Document, kick-off agenda, copies of relevant emails, meeting notes, status reports, etc.
  • Development Documents including course map, scripts, planning docs, assessments, resource documents, etc. 
  • Published Course Files including zip files AND .story files, PDFs, videos, VO files, assignment files, etc. (as relevant for each course)
  • All documentation for a project should be ‘owned’ by Michigan Virtual. If documentation is owned by an SME or partner/contractor, a copy of those documents should be made and placed into the appropriate folders. 

The Instructional Design Manager will report any changes or revisions needed to the Template Gallery documents to the CDM.

The Course Development Manager will maintain the Google Project File Structure and Project Template Documents in the Template Gallery.

The Course Development Manager will create a new project folder for a project after the project has left “Decide” in the intake process.

The Instructional Designers and Course Development Assistants will maintain the folder structure throughout the project. At the end of the project, all associated project files must be in the Google Project Folder. Any documents stored on the team members’ individual workstations can be deleted once they are uploaded into the project folder. 

Implementation 

How can course developers implement this standard? What is the process for doing so?

SL & MVLRI Developers

  1. Define Documents
    1. Project Kickoff Agenda
    2. Scope and Sequence (non-automated)
    3. Course Map Template (non-automated)
  2. Design Documents
    1. Automated Course Map
    2. Alignment Chart (automated)
    3. Syllabus Template
  3. Develop Documents
    1. Assignment Templates (folder)
      1. Assignment Template
      2. Attached Document Template
      3. Discussion Template
      4. Quiz or Test Template
      5. Course Points Spread Template
    2. Unit 1 (repeat for all units in course)
      1. Lesson Script Template
      2. Unit Introduction Template
      3. Unit Wrap Up Template
    3. Course Development Checklist Template (document)
  4. Deploy Documents
    1. Attributions Template
    2. Change Log Template
    3. Feedback Log
  5. Debrief Documents
    1. SLS Debrief Survey Template
  6. Historical Documents (folder)
  7. “A Guide to Sources for Public Domain Literature and Media” (document)
  8. Project Status Report Agenda (document)

For PL Developers

    1. Communications
      1. Documents shared from partner/SMEs
      2. Status Reports/Meeting Agenda
      3. Timeline schedules
    2. Decide
      1. Intake documents
      2. Parter intake pre-meeting agendas
    3. Define Documents
      1. Project Kickoff Agenda
    4. Design Documents
      1. Course Maps/Outlines
      2. CDM Folder
        1. Course Descriptions Documents
        2. Course Offering Information Documents
        3. SCECH Application documents
        4. Course Development Information Document
    5. Develop Documents
      1. Assignment Templates (folder)
  • Voice Over Documents
    1. Unit 1 (repeat for all units in course)
      1. Lesson Script Template
    2. Review Documents 
      1. Feedback log
      2. Pre-deployment review logs
  2. Deploy Documents
    1. Change Log Template
    2. Feedback Log
  3. Debrief Documents
    1. Debrief Survey Responses
    2. Debrief Survry Agenda
  4. Historical Documents (folder)

Template Gallery

If additional templates are needed throughout the project duration, the project member can add from the Template Gallery at any time.

  1. Navigate to the project folder where the document will live.
  2. Create a New Document:
    1. Click the “+ New” button on the left side of the screen.
  3. Access the Template Gallery:
    1. From the dropdown menu, select “Google Docs” (or Sheets, Slides, etc., depending on the type of document you want to create).
  4. Open Template Gallery:
    1. Within the selected document type (e.g., Google Docs), there should be an option “From Template”
  5. Browse Templates:
    1. Once you’re in the Docs Template Gallery, scroll down to SLS Course Development Documents. If you’re in the Sheets Template Gallery, scroll down to SLS Course Development Documents, and/or Trackers
  6. Select a Template:
    1. Click on the template you want to use. Click on it to create a new document based on the selected template.
  7. Edit and Save:
    1. The new document based on the template will open in the editor. You can now customize the document as needed. Update the title of the document.

 

Resources

What resources would help a developer implement this standard appropriately?