Every in-class Team Presentation MUST consist of a talk using an E-Poster

Each part of the project (part 1, part 2, and part 3) has an in-class presentation as a part of its grade. Due to time constraints, each team will be limited to a 10 minute presentation. The team must create an e-poster and use it during their presentation. Each person on the team must present part of the poster.

The presentation is worth 15% of your grade on the respective portion of the project. See the sections at the end of this page for specific elements that need to be in your eposter for each of the different project parts.

All students will be giving feedback to the team that is currently presenting. You will need to turn in the feedback forms to us at the end of class, and we will anonymize the feedback and give it to the groups. These feedback forms will constitute your in-class participation grade for the day. This is the form.

The purpose of the poster session is to allow you to collect and summarize your findings to date, for a general audience. This can be difficult, but it helps you better understand your data and its significance.

Your need to have "hooks" in your poster to engage your audience. For example:

  • bullet point summaries
  • quotes
  • labeled images
  • artifact models
  • clearly labeled breakdowns

Include enough detail to give a viewer the overall picture, but do NOT use full sentences and paragraphs!

You can create your poster in any presentation program. You need to make it in a standard 4:3 ratio format, and save it as a pdf that can be loaded onto the instructor's computer for display in class. Here is an example of a poster from a Carnegie Mellon School of Computer Science poster:

We will be looking for evidence of real data in your poster, presentation, and report. Phrases like, "...they usually…" indicate generalizations based on assumptions rather than real data, whereas phrases like, "Our user does X…" indicates real data. Quotes are indications of real data since fact is often stranger than fiction. Snapshots of work place settings and artifacts are indications of real data. We will also be looking for evidence of a deep understanding of your users' work practices. For example, artifact models that only label the parts, and not what they really mean to work practice, are surface-level summaries. However, artifact models that label the parts, AND include interpretations of how your users "see" and interpret the parts indicate deep understanding. Models without any breakdowns indicate surface-level understandings of work practice.

In addition to all of the above points, we will be looking at the following items when grading your presentation:
  • Introduction (capture audience interest)
  • Body (main points clear and supported, logical organization, sources cited, visual aids clear and managed)
  • Delivery (extemporaneous, enthusiastic, proper volume and rate, good articulation and eye contact)

Part 1 Specifics:

For the first part of the project, your poster should emphasize users and their needs. You must summarize:
  • Who are your users? (title, role, other information that distinguishes them).
  • Their specific task, and the goals of this task.
  • The way they currently perform this task.
  • Limitations (e.g. breakdowns or issues) in their current toolset.
  • Constraints that your proposed system must honor (cultural, technical, practical).
In addition your poster must include at least one of each of the work models (flow, sequence, artifact, physical, cultural). Depending on how much you have worked on consolidation from individual field interviews, be sure to include at least 1 consolidated model and information on how you have generalized to consolidated models. Information gleaned from your affinity diagram should also be included if you have finished creating it!

Part 2 Specifics:

For the 2nd part of the project, your poster should again emphasize users and their needs. You must summarize:
  • Remind us of who users are, their tasks, and the goals of the tasks that you have chosen to address.
  • The vision that you developed.
  • Your Personas and their Storyboards.
  • The problems your proposed system adresses and those it doesn't address.
  • Resistance that your proposed system might meet, or where it might fail in the user's culture.
  • What are the ways you think your proposed system will improve the existing practices/tools - what are some ideas you have about measuring the sucess of your proposal?

Part 3 Specifics:

For the last part of the project, your poster should still emphasize users and their needs. You must summarize:
  • Remind us of who users are, their tasks, the goals of the tasks that you have chosen to address, and your basic proposed design.
  • The evaluation methods that you used.
  • The evaluation results.
  • Your final design.
  • Any remaining issues you know about (e.g. places where your final design cannot meet cultural constraints).