OMS CS6460: Educational Technology — Summer 2017
This page provides information about the Georgia Tech OMS CS6460 class on Educational Technology relevant only to the Summer 2017 semester. Note that this page is subject to change at any time.
The Summer 2017 semester of the OMS CS6460 class will begin on May 15th, 2017. Below, find the course’s calendar, grading criteria, and other information. For more complete information about the course’s requirements and learning objectives, please see the general CS6460 page.
To help with navigation, here are some of the links you’ll be using frequently in this course:
- Tools: Udacity Sign-On | Course Library, Udacity Version | Course Library, Wiki Version | T-Square
- Wiki Pages: CS6460 Home | Summer 2017 Syllabus | Summer 2017 Full Calendar | Assignment Submission Instructions
- Assignment Descriptions: Assignments 1 & 2 | Assignments 3 & 4 | Assignment 5 | Personal Question | Class Participation
- Project Milestones: Proposal | Weekly Status Checks | Intermediate Milestones | Final Project
- Surveys: Start-of-Course Survey | Quarter-Course Survey | Mid-Course Survey | End-of-Course Survey | CIOS Survey
Course Calendar At-A-Glance
Below is the calendar for the Summer 2017 OMS CS6460 class. Note that assignment due dates are all Sundays at 11:59PM Anywhere on Earth time. We recommend changing your time zone in T-Square to show the due date in your local time. For the complete course calendar, please see the Full Course Calendar.
|Week #||Week Of||Deliverable||Assignment Due Date|
|1||05/15/2017||Introductions, Start-of-Course Survey, Assignments 1 and 2||05/21/2017|
|2||05/22/2017||Assignments 3 and 4, Peer Feedback||05/28/2017|
|3||05/29/2017||Assignment 5, Peer Feedback||06/04/2017|
|4||06/05/2017||Personal Question, Peer Feedback||06/11/2017|
|5||06/12/2017||Proposal, Peer Feedback, Quarter-Course Survey||06/18/2017|
|6||06/19/2017||Status Check 1, Peer Feedback||06/25/2017|
|7||06/26/2017||Status Check 2, Intermediate Milestone 1||07/02/2017|
|8||07/03/2017||Status Check 3, Peer Feedback||07/09/2017|
|9||07/10/2017||Status Check 4, Intermediate Milestone 2, Mid-Course Survey||07/16/2017|
|10||07/17/2017||Status Check 5, Peer Feedback||07/23/2017|
|11||07/24/2017||Final Project (Project, Paper, and Presentation)||07/30/2017|
|12||07/31/2017||End-of-Course Survey, CIOS Survey, Peer Feedback||08/06/2017|
Below are the various assessments in this course, as well as the relative importance attached to each. Note that we expect all students in this course to enter with enthusiasm and an earnest desire to contribute to both the course and the field, not simply a desire to get a grade and move on. Additionally, we expect that the projects in the course will be extremely different, and it will not be possible to create any single rubric that can apply to every student’s work.
As such, grading typically will be very general. We assess all assignments on a traditional letter grade scale; each assignment is assigned an A, B, C, D, or F. These grades correspond to how close the assignment came to meeting the expectations of the assessment (where A is ‘meets expectations’, B is ‘almost meets expectations’, etc.). If a student receives a grade below A on any assignment except the final project deliverables, they may resubmit the assignment up to two weeks after the original deadline or one week after the grade is received (whichever is later). Certain assignments are also graded differently; make sure to check the assignment pages for complete details of the assignment’s evaluation criteria.
Final grades will be calculated as an average of all individual grade components, weighted according to the percentages below. For numeric calculations, each ‘A’ is calculated as a 95, each ‘B’ as an 85, each ‘C’ as a 75, each ‘D’ as a 65, and each ‘F’ as a 55. Assignments that are not submitted at all will be calculated as a 0. Students receiving a final average of 90 or above will receive an A; of 80 to 90 will receive a B; of 70 to 80 will receive a C; of 60 to 70 will receive a D; and of below 60 will receive an F. There is no curve. It is intentionally possible for every student in the class to receive an A.
Written Assignments: 15%
The first three weeks of the semester, you will complete five short (~500 word) written assignments. These should reflect the progress you are making towards understanding a particular community and preparing to contribute to it, culminating in a high-level proposal of what you would like to work on in the remainder of the class. These assignments are intentionally somewhat personal and casual; you may think of them something like ‘journal’ assignments, and you are encouraged to speak in first person and reflect on your progress in addition to your growing content knowledge. By the time you reach the end of these assignments, you’ll have selected either the research or development tracks, and you’ll have a high-level idea of your project. You’ll deliver the first and second pairs of assignments together, and each deliverable is worth an equal portion of the 15% (5% each). For a complete description of the written assignments, see the pages dedicated to assignments 1 and 2, assignments 3 and 4, and assignment 5.
Personal Question: 10%
Once you have explored and identified a general project area you would like to emphasize, your mentor will pose to you a targeted question about the chosen community. Your answer to this targeted question should reflect your understanding of the community, your ability to reason about the community, and your understanding of the broader issues facing the community. This question is where you should demonstrate your ability to converse in this community; therefore, your answer to this question is expected to be more polished and academic. You should certainly include citations to related work, and you should generally avoid speaking in first-person. For a complete description of the personal question, see its dedicated page.
Project Proposal: 10%
After completing the first portion of the class, you will propose your project, either individually or in a group. You should lay out a broad description of the motivating principles and objectives of the project, a clear statement of what work will be done, a week-by-week plan for completing that work (including separating individuals’ responsibilities in the case of group projects), a description of the intermediate milestones to be delivered, and a description of the ultimate contribution that will be delivered. Your mentor will then work with you to scope your proposal, address any potential issues, ensure the feasibility of the project plan, and ultimately approve your proposal. Because your proposal is personal to the work you plan to do, writing in first-person is acceptable; however, it should be polished and academic, including references to related research. For a complete description of the project proposal, see its dedicated page.
Project Weekly Status Checks: 5%
Each week, you will submit a short, individual status check. If you are in a group, each member of the group will submit their own status check. The purpose of the status check is to ensure progress is being made on a weekly basis in accordance with the plan outlined in the proposal, to identify early on if group members are not fulfilling their roles, and to recover if unexpected obstacles arise. For a complete description of the weekly status checks, see their dedicated page.
Intermediate Milestones: 15%
While working on your project, you will deliver two intermediate milestones, to be delivered in weeks 7 and 9. These intermediate milestones serve two purposes: one, they are to demonstrate to your mentor the progress you are making, and two, they are to give you the opportunity to receive feedback from your peers and mentor. You will describe the milestones you will deliver in your project proposal. If you select the research track, we recommend your first milestone be your experimental plan, and your second milestone be your preliminary data analysis. If you select the development track, we recommend your first milestone be low-fidelity prototypes, and your second milestone be higher-fidelity prototypes. If you select the content track, we recommend your first milestone be your detailed curriculum design, and your second milestone be some of your early content. These recommendations are flexible, however, and may differ based on your specific project. You should think primarily about what kind of feedback you anticipate needing and ensure that your intermediate milestones will allow you to receive that kind of feedback. Your mentor will approve your intermediate milestones as part of approving your proposal. For a complete description of the intermediate milestones, click see their dedicated page.
Final Project: 30%
At the end of the semester, you or your group will deliver three things: the project itself, a presentation of the project, and a paper in the format most pertinent to your project. The nature of the deliverable will differ based on your project. If you select the research track, the deliverable will be the research instruments, data, and analysis. If you select the development track, the deliverable will be the working tool itself. The presentation is meant to present the project to your classmates and, if you agree, to future students in the class. The paper is meant to present the project to potential conferences, journals, or investors, if you choose to use it that way. The project itself is worth two-thirds of your project grade (20% of your overall grade), while the paper and presentation are each worth one-sixth of your project grade (5% of your overall gradeeach). For a complete description of the final project and its two accompanying deliberables, see its dedicated page.
Because this course is driven by the community of students, participation is required and assessed explicitly. Participation can come in many forms: interacting and posting on Piazza; contributing new articles and information to the class library; completing class surveys; completing Peer Feedback tasks; participating in conversations via other tools; participating in your classmates’ experiments and beta tests; and more. Generally, participation is simply anything you do to make the class better for everyone else. Participation will be evaluated according to a point system described on the Class Participation assignment page. For a complete description of the participation policy, see its dedicated page.
The following policies are binding for this course.
We have an incredible team of mentors helping out with this course. However, all our mentors are busy professionals with jobs, families, and OMS classes of their own. Each mentor will be assigned roughly 15 students, and each student should expect to effectively receive around 30 minutes of dedicated mentor time each week for the duration of the semester. This time includes time spent reading assignments and writing feedback.
Because of this, we ask that you be respectful and efficient with mentors’ time. Remember that live conversations generally take up more real-time commitment than asynchronous communications that can be squeezed in during short breaks or at strange times. Work or family obligations may sometimes prevent mentors from responding within a couple days. Most importantly, note that with a few clearly-defined exceptions (providing the personal question, approving the project proposal), nothing you do in this class is dependent on the mentors. If absence of feedback or communication with your mentor becomes an issue, that should not be considered an excuse not to complete any assigned work. It may be taken under consideration with regard to the quality of your work, but waiting on feedback is not an excuse to fail to move forward.
Finally, there may be times when we need to shift mentors around. For example, if you get together with a few other students for a group project, we’ll rearrange those partnerships so that one mentor can work with everyone on that project. Or, if a person’s interests change and end up aligning very closely with a different mentor, we may move people around then as well. Finally, if drops or anything result in the load being very imbalanced between mentors, we may make switches then.
We don’t anticipate issues here, but we believe it’s better to set these expectations in advance than to have to write policies governing these things later.
Official Course Communication
You are responsible for knowing the following information:
- Anything posted to this syllabus (including the pages linked from here).
- Anything posted to the general course landing page.
- Anything emailed directly to you by the teaching team (including announcements via Piazza), 24 hours after receiving such an email.
Because Piazza announcements are emailed to you as well, you need only to check your Georgia Tech email once every 24 hours to remain up-to-date on new information during the semester. Georgia Tech generally recommends students to check their Georgia Tech email once every 24 hours. So, if an announcement or message is time sensitive, you will not be responsible for the contents of the announcement until 24 hours after it has been sent.
We generally prefer to handle communication via Piazza to help with collaboration among the teaching team, but we understand Piazza is not ideal for having information “pushed” to you. We may contact you via a private Piazza post instead of an email, but if we do so, we will choose to send email notifications immediately, bypassing your individual settings, in order to ensure you’re alerted. As such, this type of communication will also fall under #3 above.
Note that in three years as a Georgia Tech OMSCS instructor, I’ve encountered exactly one instance of a time-sensitive email; so, the 24-hour rule likely won’t ever be relevant. As with other things, however, we believe it’s better to be clear at the beginning rather than write policies later.
Note that this means you won’t be responsible for knowing information communicated in several other methods we’ll be using. You aren’t responsible for knowing anything posted to Piazza that isn’t linked from an official announcement. You aren’t responsible for anything said in HipChat, Slack, or other third-party sites we may sometimes use to communicate with students. You don’t need to worry about missing critical information so long as you keep up with your email and understand the documents on this wiki.
This semester, we’ll be using Slack for office hours. If you are unaware, Slack is a popular team communication chat tool that allows conversations in public rooms, private rooms, and private messages. Slack office hours are times when the instructor and/or one or more teaching assistants will be available on the dedicated CS6460 student Slack community. You can sign up for the student Slack community at omscs6460.slack.com.
During Slack office hours, the instructor and/or mentors in attendance will be available for conversations in the public #office-hours channel, or in private one-on-one channels. When necessary, Hangouts, Skype calls, or other forms of conversation can be launched from Slack office hours. You are also encouraged to use the Slack community for discussions, project work, or anything else. The instructors and/or TAs will be available during office hours, but they may also be available at other times as well.
The calendar of office hours for OMS CS6460 can be found on this dedicated Google calendar. Changes to any given office hours session will always be made at least 24 hours in advance; if late changes are needed, they’ll be announced with an announcement. If you are not comfortable signing up for Slack to participate in Slack office hours, you may also feel free to email or post privately on Piazza to set up a chat via an alternate technology at the same time. If you would like to participate in office hours but are unable to make the given times, feel free to email or post privately on Piazza and we’ll try our best to accommodate you.
The student-driven and open-ended nature of this class means that deadlines are not quite as important here as they would be in other classes. However, deadlines and weekly routines help our mentors spend the majority of their time interacting with students and a minority handling administrative and organizational tasks. Therefore, we cannot accept late work.
We have made the descriptions of all assignments available on the first day of class so that if there are expected interruptions (business trips, family vacations, etc.), you can complete the work ahead of time. In proposing your project, you are welcome to include external constraints in the planning process and build in time where you know you won’t be able to work on your project.
Of course, emergencies (illness, family emergencies) will happen. In those instances, please contact the Dean of Students office. The Dean of Students is equipped to verify emergencies and pass confirmation on to all your classes. For consistency, we ask all students to do this in the event of an emergency.
The primary objective of this class is to produce a contribution to the field of educational technology. As such, it is acceptable to leverage existing code, libraries, resources, and information to use as pieces for your projects, reflections, and presentations. After all, part of joining a research community is building on what the community has already produced.
However, it is critical that your contribution be evaluated on what you have contributed. As such, anything that is borrowed from existing resources must be cited. In all written work, such as reflections and final reports, sources should be cited in APA style, both in-line and at the end of the document. Please consult the Purdue OWL for information on when and how to cite sources in research. When in doubt, don’t hesitate to ask!
Similarly, any resources used in the production of software tools should be cited as well. If you copy code to use within your project, cite the source of the code in a comment alongside the copied code. Include a link to the original source of the code and clearly note where the copied code begins and ends (for example, with
/* BEGIN CODE FROM (source link) */ before and
/* END CODE FROM (source link) */ after the copied code). Any external libraries, images, or any other materials not created by you should be referenced either within the code (where possible) or in a README file included with the deliverable.
As mentioned previously, this course is as much an experiment in educational technology as it is a class on educational technology. First, because this class is experimental and we are continually striving to improve it, there are bound to be things that go wrong. We ask your patience and support as we figure things out, and in return, we promise that we, too, will be fair and understanding, especially with anything that might impact your grade or performance in the class. Second, we want to consistently get feedback on how we can improve and expand the course for future iterations. You can take advantage of the feedback box on Piazza (especially if you want to gather input from others in the class), give us feedback on the surveys, or contact us directly via private Piazza messages.