<?xml version="1.0" encoding="utf-8" standalone="no"?>
<!DOCTYPE document PUBLIC "-//CNX//DTD CNXML 0.5 plus MathML//EN" "http://cnx.rice.edu/technology/cnxml/schema/dtd/0.5/cnxml_mathml.dtd">
<document xmlns="http://cnx.rice.edu/cnxml" xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/" xmlns:m="http://www.w3.org/1998/Math/MathML" id="new">
  <name>Procedures to Clarify Expectations - Principle 6 - Promising Practices</name>
  <metadata>
  <md:version>1.1</md:version>
  <md:created>2008/06/30 13:20:38.787 GMT-5</md:created>
  <md:revised>2008/06/30 13:47:11.068 GMT-5</md:revised>
  <md:authorlist>
      <md:author id="krestine">
      <md:firstname>Keith</md:firstname>
      <md:othername>A.</md:othername>
      <md:surname>Restine</md:surname>
      <md:email>krestine@twu.edu</md:email>
    </md:author>
  </md:authorlist>

  <md:maintainerlist>
    <md:maintainer id="krestine">
      <md:firstname>Keith</md:firstname>
      <md:othername>A.</md:othername>
      <md:surname>Restine</md:surname>
      <md:email>krestine@twu.edu</md:email>
    </md:maintainer>
  </md:maintainerlist>
  
  <md:keywordlist>
    <md:keyword>Blackboard</md:keyword>
    <md:keyword>Distance Education</md:keyword>
    <md:keyword>Faculty Development</md:keyword>
    <md:keyword>Online Teaching</md:keyword>
  </md:keywordlist>

  <md:abstract>This module describes some policies that you may wish to develop for your course.</md:abstract>
</metadata>
  <content>
    <para id="element-289"><name>Procedures</name>Create a policy for early posting. Some students want to work ahead of the group and to get many of the activities out of the way. This is your decision but clearly define what you will accept and what is not allowed in the course. Another way to approach this is to release material on a scheduled basis so students can only see the material as you allow. Students not actively participating with other students are not supporting other students and miss some of the interaction and learning found through the online environment.
 </para><para id="element-281">Create a policy for late assignments and missed examinations. Some instructors implement policies that do not accept late work while others allow reduced credit.

 </para><example id="element-402"><name>Assignment Policy</name><para id="element-372">
  All assignments will be submitted via Blackboard. This means you will upload a file to Blackboard. I will then grade that assignment using Track Changes in Word, and return the graded file to you. Since Blackboard has time and date stamp capabilities, it will be the final record of when an assignment was received. All weekly postings are due by 8:00 a.m. on Wednesday. Postings will be submitted via the discussion board. The discussion board will be checked weekly on Wednesday mornings to determine whether posting requirements were fulfilled on time.</para><para id="element-782">LATE ASSIGNMENTS AND/OR POSTINGS WILL NOT BE ACCEPTED</para>
</example><para id="element-805">Use assignments that require approved topics, draft versions, peer editing, etc. to emphasize issues of quality. You might see these called incremental progress assignments in some of the literature. The idea is to allow students to see where they should be in the project at a particular date. Use some type of checkpoints for long-range assignments to help students stay on track. Announcements work well to remind students that preliminary materials (topics for papers, rough drafts, etc) are required at specific times throughout the semester. You might also post these using the Calendar function. Incremental progress assignments are also good as a feedback mechanism, allowing you to identify and clarify misunderstandings early in the project.  </para><para id="delete_me">
       <!-- Insert module text here -->
    </para>   
  </content>
  
</document>
