Project M (Spring 2020) Cancelled for Spring 2020
Answer the following prompt in a maximum of 30 pages (excluding references and excluding personal reflections) in JDF format. Any content beyond 30 pages will not be considered for a grade. 30 pages is a maximum, not a target; our recommended per-section lengths intentionally add to less than 30 pages to leave you room to decide where to delve into more detail. This length is intentionally set expecting that your submission will include diagrams, drawings, pictures, etc. These should be incorporated into the body of the paper unless specifically required to be included in an appendix.
If you would like to include additional information beyond the word limit, you may include it in clearly-marked appendices. These materials will not be used in grading your assignment, but they may help you get better feedback from your classmates and grader. For example, you might include copies of previous assignments, copies of your surveys, raw data, interview transcripts, raw notes, etc.: anything that does not directly address the assignment’s questions, but rather helps understand your progress as a whole.
Over the last few weeks, you’ve individually gone through one iteration of the design life cycle in your chosen area. For the final team project, you, together with your teammates, will iterate through it again, either continuing one (or more) of your individual ideas or examining a new task, interface, or problem. Rather than walking slowly step-by-step through the design life cycle the way you did for the individual assignments, instead you will deliver the results of this iteration all together at the end. This should leave you the flexibility to schedule and distribute labor as necessary to complete your project. Your final deliverable should include the following sections. The percentages indicate the percentage of the grade contributed by each portion of the project.
- Abstract (5%). Begin your final deliverable with a summary of the overall project. Briefly describe the problem, the needfinding approaches, the prototypes, the evaluation strategies, and the salient results.
- Introduction (5%). Briefly introduce the problem area that you are addressing. Provide the necessary background for the reader to understand the following sections. Do not assume the reader is another OMSCS student (if, for example, you’re redesigning Piazza, do not assume the reader has used Piazza before).
- Needfinding Planning (10%). Outline a plan for needfinding. You should borrow from M1 for the structure and coverage of this section, but you do not need to select exactly three methods: you may select more or less depending on what information you need to gather, but make sure to justify your plan.
- Needfinding Execution (5%). Execute the needfinding plan outlined above and report the results. Borrow from M2 for the structure and coverage of this section. Again, you do not need to perform exactly three needfinding exercises, but you should report on the ones you perform similar to how you did in M2.
- Data Inventory and Requirements Definitions (5%). Based on your needfinding execution, synthesize your results into a data inventory covering what you learned and the requirements those results dictate for your ultimate interface.
- Design Alternatives (10%). Perform both individual and group brainstorming activities for design alternatives. Outline a general brainstorming plan, including rules for individual brainstorming, a plan for group brainstorming, and heuristics for selecting from these alternatives.
- Prototyping (20%). Prototype at least two of your ideas. Aim for medium fidelity; even though you may not be ready for medium fidelity based on the needfinding you’ve done so far, this is still a good chance to practice polished wireframes, card prototypes for several screens and tasks, or physical prototypes. If these are not possible, more complete Wizard of Oz prototypes are also acceptable. Functional prototypes are also acceptable and encouraged, but not required. You may use the same type of prototyping for both prototypes, but otherwise borrow from the second half of M3 for the structure and coverage of this section.
- Evaluation Planning (10%). Plan your evaluation approach for these two prototypes. Use the same evaluations on both prototypes if possible to facilitate direct comparison between the two. You should evaluate the prototypes in multiple ways; these could be multiple evaluations within the same category (e.g. interviews, surveys, and think-aloud protocols), or they could be multiple evaluations across categories (e.g. think-aloud protocols, an experiment, and a heuristic evaluation). While predictive evaluation may be employed, your evaluation should not only be predictive evaluation; every group should include either qualitative or empirical (or both). Borrow from M4 for the structure and coverage of this section, and make sure to justify the evaluations you selected.
- Evaluation Execution (10%). Execute your evaluation plan and report the results. Borrow from M5 for the structure and coverage of this section.
- Conclusion (20%). Summarize the findings from this iteration through the design life cycle, emphasizing how the understanding of the user, model of the problem, and design of an interface have evolved. Then, outline what the next steps of your project would be if this cycle was to continue. What new questions are there about the user? What is the next step for the prototype development, increased fidelity or testing new improvements and changes? What type of evaluation would you be ready to use after those changes?
At the end of the project deliverable (after all other content, the last N pages), each member of the group should write a one-page individual reflection. Each member’s individual reflection should cover the following three things:
- What you individually contributed to the project.
- What each of your teammates contributed to the project.
- Your overall reflections on how the project progressed: what worked well, what could have worked better, and what you wish you had known prior to the start of the project.
Your individual reflection will be graded as a multiplier on your individual project score. The grade will primarily (but not exclusively) be based on the relative size of each member’s contribution; deductions will generally be reserved for particularly dramatic cases of uneven contributions. Note that the individual reflections are appended to the project deliverable itself; you should thus expect your teammates to review your statement of your contribution, as well as to review your teammates’ statements. Failure to include an individual reflection may be penalized by a multiplier as low as 0 (meaning a grade of 0 on the project).
Complete your assignment using JDF, then save your submission as a PDF. Assignments should be submitted to the corresponding assignment submission page in Canvas. You should submit a single PDF for this assignment. This PDF will be ported over to Peer Feedback for peer review by your classmates. If your assignment involves things (like videos, working prototypes, etc.) that cannot be provided in PDF, you should provide them separately (through OneDrive, Google Drive, Dropbox, etc.) and submit a PDF that links to or otherwise describes how to access that material.
This is a group assignment. Only one person from your group needs to submit. Please make sure to list your group number in the assignment body. Make sure to cite any sources you reference, and use quotes and in-line citations to mark any direct quotes.
Late work is not accepted without advanced agreement except in cases of medical or family emergencies. In the case of such an emergency, please contact the Dean of Students.
Your assignment will be graded on a 100-point scale coinciding with a rubric designed to mirror the question structure. Make sure to answer every question posted by the prompt. Pay special attention to bolded words and question marks in the question text.
After the project deadline, you will be asked to review the relative contribution of each of your teammates. These evaluations will be taken into consideration in assigning project grades. If a team agrees that a member contributed significantly less to the project than expected, that team member may be penalized up to their entire Project M grade.
After submission, your assignment will be ported to Peer Feedback for review by your classmates. Grading is not the primary function of this peer review process; the primary function is simply to give you the opportunity to read and comment on your classmates’ ideas, and receive additional feedback on your own. All grades will come from the graders alone.
You will typically be assigned three classmates to review. You receive 1.5 participation points for completing a peer review by the end of the day Thursday; 1.0 for completing a peer review by the end of the day Sunday; and 0.5 for completing it after Sunday but before the end of the semester. For more details, see the participation policy.