|
General Notes:
- Parallel sub-phase 3.1 will be a
voice-over-slides
team presentation
video
about their own prototype.
My plan is to put these, or a subset of these, up on ELMS for peer
viewing after they are submitted.
- Parallel sub-phase 3.2 will be
a heuristic evaluation
of another team's Phase 2.2 prototype
and the design of a user study about it.
I will post
the pairings of team to team
and contact info on Slack.
Note that this will not be bidirectional, so you will not be evaluating
the Phase 2 of the team that is evaluating your Phase 2.
Overview:
The evaluation sub-phase is not connected to the presentation sub-phase.
The immediate purpose of the evaluation sub-phase of this project
is to give you experience at:
- performing a heuristic evaluation of a prototype with a team
- designing a user study (even though there will be no execution of it)
In addition to turning it in to us on ELMS, your group will also deliver
your report to the team whose Phase 2.2 you are using for your Phase 3.2.
However, your heuristic evaluation and usability study design (and report)
will be
used to determine your Phase 3.2 grade. They will not be used
to alter the other team's Phase 2.2 grade. They will, however, be
very useful to the team to better consider their design thinking and
approaches.
For parallel sub-phase 3.1 you will need to
create a voice-over-slides video, and PDF of the slides with the
narration transcribed below each.
The individual slides will be a mixture of text and screenshots
from your prototype.
To show the flow through tasks, you can either
have several slides in a row with screenshots as you
undertake the task,
or you can put a screen capture video onto a slide
as well.
The video presentation should be between 8 and 15 minutes.
-
Tools that I recommend using to make the video:
PowerPoint,
Audacity,
a microphone.
-
The process that I recommend for making your 8-15 minute video:
- Prepare your slide set as a team, using Google Slides
as a shared working space. This might include slides with
a screenshot of something or a photo of something or just text.
- Decide who on the team will present each slide.
Then each person goes through their slides as if they were presenting
each slide during a team presentation in class,
transcribing what they would say in the "slide notes"
space below each slide.
- Everyone on the team should review the full transcript when everyone
feels done to lock it in. Then, each student will record the audio for
their slide and one student will collect the audio file for each slide
to create the full video in PowerPoint.
- For each slide a student is narrating, have Audacity open in a small
window so you can see the notes area of slides behind it, and narrate
the slide using that script. Then save the track out as an MP3
or WAV named for the slide number in which it will go.
- For the student combining everything, go through each slide and
insert the corresponding audio clip on that slide, and move the
icon off to the slide so it doesn't actually appear on the slide.
- After having the whole slideset done and saved, go through and
make a video
by going to File - Save&Send or Export (depends on PowerPoint
version), and choosing the option to Create a Video at Internet
resolution.
- Finally, go through and update your narration script
in the notes section to match the recorded dialog, and then
print the slide set with the notes as a PDF handout to post,
as I have been doing with my video lessons.
-
It can be good to add "pause" points in your video where you ask the
viewer to pause if they want to study the slide more before the video
moves onto the next one.
For parallel sub-phase 3.2 you will need to provide us with several things,
all submitted as a PDF.
- your team members need to undertake a heuristic evaluation
of the prototype provided to you by the other team; this will
require each individual on the team undertaking an evaluation
(the first section of the PDF),
and then the team coming together (I suggest you do this in
a Zoom or other video chat meeting) to combine their findings
into a single report (the second section of the PDF)
- your team will design a user study, providing
us with a detailed description of the plan, complete
with techniques, scripts, etc. and a consent form,
and
this semester for social distancing reasons only
"pilot" it online "on" one of the members of your team and
describe that experience from both sides
(the third section of the PDF)
For the heuristic evaluation, the members of your team will undertake the
role of HCI experts brought in to review a prototype. Because of the
economy of these methods, you are expected to be able to apply them in
your actual work practices. The other team can (and should) provide you
with a list of tasks their prototype supports, but your evaluation can
also address things such as any in the horizontal levels not mentioned
in their tasks if you see them as common tasks or vertical aspects that
you can tell aren't in the current design but you feel need to be.
The methods used in the usability study you design can include strict
observation, think-aloud, constructive interaction, questionnaires,
and interviews. Your team needs to determine the techniques it feels
will be best used for the user study of the project you are assigned,
but the expectation is a mixture of methods.
The "Who did what" report is to be turned in on the
same day as Phase 3.2 is due.
This is likely to be a one to two page summary of who in the
group did what. For each person, explain what portions of the project
they worked on, what they wrote, portions of code, documents, etc. This
is a public document that you must all work to agree upon.
Like the Phase 2 report should have
a salary section and aim to be forthright.
Grading Note
The elements of this phase will be worth 10 of the 40
percentage points that the team project makes of the
semester grade.
Updates
If any updates to the description are required, they will
be announced on places like Slack as well as the class
website.
|