|
-
Set everyone team member up on sourceforge.net.
-
Resolve remaining questions about the project proposal.
-
Talk about user visit reports.
-
Setting up account for Sam and Forest. Everyone should be on
sourceforge.net now.
-
Talked a little about Sourceforge and CVS. People should go home
and see if they can access the CVS server.
-
There's a
homepage
for this
project, generated by
Maven
.
-
Go through each point on the project proposal. We're focusing
more on the storytelling side instead of just organization.
-
Sam and Forest both has a friend who does a lot of digital
photography. They're going to be our test users.
-
Go through the items in the user visit plan. We first going to
introduce ourselves and what we're doing, then ask the users to
go through the whole workflow from how they acquire their
pictures to publishing them on-line for people to see. We then
would ask them to evaluate each of the steps in the workflow, and
observe where they have the most troub
le.
-
In particular, we need to observe the following things:
-
The general workflow
-
At what point the user would get stuck doing certain
things. This is unlikely for both users are pretty
experienced.
-
At what point the user would perform certain tasks
repeatedly.
-
The number of substeps that the user take to go from
downloading the pictures to publishing on-line.
-
If users have made mistakes, what the mistakes are and how
they recover from them.
-
See the project's proposal and user test plan for details.
-
Sam is going to type up her notes on both the proposal and the
user test plan. She'll then send it to the team.
|