OMS CS6460: Educational Technology — Summer 2021
This page provides information about the Georgia Tech OMS CS6460 class on Educational Technology relevant only to the Summer 2021 semester. Note that this page is subject to change at any time. The Summer 2021 semester of the OMS CS6460 class will begin on May 17, 2021. 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: Research Guide & Course Library | Canvas | Peer Feedback | PeerSurvey
- Course Pages: CS6460 Home | Summer 2021 Syllabus | Summer 2021 Full Calendar | Course FAQ | Class Participation
- Assignment Descriptions: Assignment 1 | Assignment 2 | Assignment 3 | Qualifier Question | Class Participation
- Project Milestones: Proposal | Weekly Status Checks | Intermediate Milestones | Project | Presentation | Paper
Course Calendar At-A-Glance
Below is the calendar for the Summer 2021 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 Canvas 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/17/2021||Start-of-Course Survey, Assignment 1||05/23/2021|
|4||06/07/2021||Qualifier Question, Quarter-Course Survey||06/13/2021|
|6||06/21/2021||Weekly Status Check 1||06/27/2021|
|7||06/28/2021||Weekly Status Check 2, Intermediate Milestone 1||07/04/2021|
|8||07/05/2021||Weekly Status Check 3, Mid-Course Survey||07/11/2021|
|9||07/12/2021||Weekly Status Check 4, Intermediate Milestone 2||07/18/2021|
|10||07/19/2021||Weekly Status Check 5||07/25/2021|
|11||07/26/2021||Project, Presentation, Paper||08/01/2021|
|12||08/02/2021||End-of-Course Survey, CIOS Survey||08/08/2021|
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, assignment descriptions are very general, and grading criteria will vary from project to project. Consistency is instead supplied by the structure of the course: every student should resubmit any subpar work where permissible, secure their mentor’s agreement on their proposal, and complete weekly status checks to adjust expectations and agree on deviations from the proposal.
Historically, any student who has not received an A has not fulfilled at least one of those three obligations. We assess all assignments on a 11-point scale, 0-10. These grades correspond to how close the assignment came to meeting the expectations of the assessment: 10 is “exceeds expectations”, 9 is “meets expectations”, 8 is “almost meets expectations”, and so on. If a student receives a grade below 9 on any assignment (excluding milestones and the final project deliverables), they may resubmit the assignment up to one week after the grade is received. Resubmissions may receive up to a 9.
Final grades will be calculated as an average of all individual grade components, weighted according to the percentages below. 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 few weeks of the semester, you will complete three written assignments. These serve two purposes: they show your overall progress toward settling on an idea to pursue for your project, and they train you on some of the specific skills you’ll need to execute the remaining assignments in the course. By the time you reach the end of these assignments, you’ll have selected either the research, development, or content track, and you’ll have a high-level idea of your project. Each assignment is worth an equal portion of this 15%. For a complete description of the written assignments, see the pages dedicated to assignment 1, assignment 2 and, assignment 3.
Qualifier 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 qualifier question, see the dedicated qualifier question 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 (10%)
While working on your project, you will deliver two intermediate video milestones, roughly one-third and two-thirds of the way between the proposal and the final project deadlines. 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. Both milestones should be videos including narration: you should show off the progress you’ve made and ask for what feedback you need. In addition to the video, you are welcome to include survey drafts, experimental plans, wireframes, etc. on which you would like feedback, but the primary focus of the milestone should be your video presentation. For a complete description of the intermediate milestones, click see their dedicated page.
Final Project (20%), Paper (10%), and Presentation (5%)
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. 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. If you select the content track, the deliverable would be the content that you developed. 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 three components of the final project are not weighted evenly; the final project itself counts for 20% of your final grade; the final paper counts for 10%; and the final presentation count for 5%. For a complete description of the final project and its two accompanying deliverables, the dedicated pages for the project, paper, and presentation.
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 the course forum; 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 20 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. Most importantly, note that with a few clearly-defined exceptions (providing the qualifier 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 will 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, such as the general course landing page).
- Anything emailed directly to you by the teaching team (including announcements via the course forum or Canvas), 24 hours after receiving such an email.
Generally speaking, we will post announcements via Canvas and cross-post their content to the course forum; you should thus ensure that your Canvas settings are such that you receive these announcements promptly, ideally via email (in addition to other mechanisms if you’d like). 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 the course forum to help with collaboration among the teaching team, but we understand the course forum is not ideal for having information “pushed” to you. We may contact you via a private the course forum 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 #2 above.
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 the course forum that isn’t linked from an official announcement. You aren’t responsible for anything said in Slack or any 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 web site. This also applies in reverse: we do not monitor our Canvas message boxes and we may not respond to direct emails. If you need to get in touch with the course staff, please post privately to the course forum (either to all Instructors or to an instructor individually) and tag the instructor in the relevant post.
Communicating with Instructors and TAs
Communication with the course teaching team should be handled via the discussion forum. If your question is relevant to the entire class, you should ask it publicly; if your question is specific to you, such as a question about your specific grade or submission, you should ask it privately. Most private questions should be directed specifically to your mentor and can be submitted in your mentor thread.
Our workflow is to regularly filter the forum for Unresolved posts, which includes top-level threads with no answer accepted by the original poster, as well as mega-threads with unresolved follow-ups. If your question requires an official answer or follow-up from an instructor or teaching assistant, make sure that it is posted as either a Question or as a follow-up to a mega-thread, and that it is marked Unresolved. Once an instructor or TA has answered your question, it will automatically be marked as Resolved; if you require further assistance, you are welcome to add a follow-up, but make sure to unmark the question as Resolved in order to make sure that it is seen by a member of the teaching team.
Similarly, in order to keep the forum organized, please post as a Post or Note instead of a Question if your question does not require an official response from the teaching team. For example, if you are interested in getting multiple perspective from classmates, getting feedback on your ideas, or having a discussion that does not have a single answer, please use Post or Note instead of Question. Please reserve Question threads for questions that will likely have a single official response. TAs and instructors will regularly convert Questions to Posts or Notes that do not need a single official answer, but it will save time and allow them to focus their attention on other students if you correctly categorize your post in the first place.
Although this class is largely self-directed, deadlines and weekly routines help our mentors spend the majority of their time interacting with students and a minority handling administrative and organizational tasks. 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.
If due to a personal emergency, health emergency, family emergency, or other unforeseeable life event you find you are unable to complete an assignment on time, please post privately to your mentor in your mentor thread with information regarding the emergency. Depending on your unique situation, we will share guidance on how to proceed; if the emergency is projected to delay a significant quantity of the work required for the class, we may recommend withdrawing and reattempting the class at a later date. If the emergency will likely only impact a small amount of the course, we may be able to accept the work late as a one-time exception. If the emergency takes place once you have already completed a significant fraction of the coursework, we may offer an Incomplete grade to allow you to finish the class after the semester is over.
Note that depending on the nature and significance of the request, we may require documentation from the Dean of Students office that the emergency is sufficient to justify offering an incomplete grade or accepting late work. Note also that regardless of the reason, we also cannot promise any particular turnaround time for grading work that was approved to be submitted late; it may be that grades and feedback will not be returned before the end of the term, and it may be that a temporary grade of Incomplete must be entered to leave time to grade work that was accepted late.
If you are not comfortable sharing with us the nature of an emergency, or if you need more comprehensive advocacy, we ask you to go through the Dean of Students’ office regarding class absences. The Dean of Students is equipped to address emergencies that we lack the resources to address. Additionally, the Dean of Students office can coordinate with you and alert all your classes together instead of requiring you to contact each professor individually. The Dean of Students is there to be an advocate and partner for you when you’re in a crisis; we wholeheartedly recommend taking advantage of this resource if you are in need. You may find information on contacting the Dean of Students with regard to personal emergencies here: https://gatech-advocate.symplicity.com/care_report/
All students in the class are expected to know and abide by the Georgia Tech Academic Honor Code. Specifically for us, the following academic honesty policies are binding for this class:
- In written essays, all sources are expected to be cited according to APA style, both in-line with quotation marks and at the end of the document. You should consult the Purdue OWL Research and Citation Resources for proper citation practices, especially the following pages: Quoting, Paraphrasing, and Summarizing, Paraphrasing, Avoiding Plagiarism Overview, Is It Plagiarism?, and Safe Practices. You should also consult our dedicated pages on how to use citations and how to avoid plagiarism.
- Any non-original figures must similarly be cited. If you borrow an existing figure and modify it, you must still cite the original figure. It must be obvious what portion of your submission is your own creation.
- Any programming resources, such as existing code or libraries, must be cited as well. 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 the projects you complete in this class are highly personal and original, you are permitted to share them publicly when the semester is over. However, by participating in this class you authorize us to pursue the removal of your content if it is discovered on any public assignment repositories, especially if it is clearly contributed there by someone else.
These policies, including the rules on all pages linked in this section, are binding for the class. Any violations of this policy will be subject to the institute’s Academic Integrity procedures, which may include a 0 grade on assignments found to contain violations; additional grade penalties; and academic probation or dismissal. Note that if you are accused of academic misconduct, you are not permitted to withdraw from the class until the accusation is resolved; if you are found to have participated in misconduct, you will not be allowed to withdraw for the duration of the semester. If you do so anyway, you will be forcibly re-enrolled without any opportunity to make up work you may have missed while illegally withdrawn.
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 the course forum (especially if you want to gather input from others in the class), give us feedback on the surveys, or contact us directly via private the course forum messages.