Meeting summary and notes

Okay, so four of us met with Mike today. I'll just try and summarise what was covered:

• We need to make sure we're covering the formal stuff. This page on the module page seems to cover what we need. Task analysis still needs fleshing out.
• So far, our prototype seems to be fine, but we need to get it finished so we can try it out on our users.
• The video footage, showcasing a couple of scenarios and how the system would respond, seems to be a good idea. Mike also suggested a cognitive walkthrough of the system from the perspective of one of our personas. When it's done, video footage can be placed on youtube and embedded in the blog posts.
  

To-do list for this week

• Andy's still missing a few sets of screens for the prototype. If you haven't got them to him yet, please do so as quickly as possible so we can get the prototype finished!
• Although we have use cases, they need to be construed in a more formal task analysis format. Since I did the use cases, I may as well do that as well.
• Prepare questions to pose to our personas for feedback on the prototype, if we're going to do this in conjunction with the video footage.
• Add 'technical ability' and 'goals' to your personas, if you haven't already.
• With regards to the video footage, I have access to a digital camera that should suffice for the task. I also can get hold of a flat-cap and, if needed, a walking stick :) But we still need to decide which scenarios we're going to play out. Mike suggested focusing on a couple of good ones, and writing out the rest. We can probably derive them straight from the use cases, or the task analysis when I post it up.

Discuss/volunteer for tasks away!

Meeting Tomorrow

In case people haven't seen it yet, we have a meeting at 12.45 tomorrow with Mike in the usual place.

On another note, based on what the lecture was on - do people think our personas are detailed enough? I think they mostly are, but perhaps we all ought to include things like technical ability and goals... This week we need to test our prototype on our personas, so we need to ensure that they are as detailed as possible so we can get into character. I personally think if we have one person pose some questions regarding the prototype, then everyone could answer them in character? (As was suggested in the lecture).

Meetings 21/2/07

Just a quick summary and comments on what we spoke about today (yesterday as I post):

1) I spoke with Russel about the stop motion animation as an idea for our prototype, I got a few pointers about how to go about how to make it a user centered prototype. This was mainly to only show features and aspects that the prospective user will be interested in... He also mentioned about installation of the system and so perhaps a knock together of a few shots showing an idea of that.

2) We've got quite far in the project and for the prototype we really need to have first set firmly the features we want to focus on the system having, this is so we can start to look at them in more detail and essentially design them in more detail. Perhaps we need to divide up the features such that a different person looks at one or two features and posts up any findings be they good or bad, this would allow other members of the group to offer solutions or other comments.

3) Our blog and its purpose... This is quite key, we as a group discuss everything in the meetings, solve it and go away to create it posting the results on the blog. This isn't helpful for people looking to see the process we've been through since it all happens when we meet up. Any ideas on how to make the blog serve the purpose its designed for(while not detracting from our current ability to solve problems), would be welcome.

Meeting 19/02/07

All team members present.

Andy, I'm unable to emailing the photos to your uni account - anywhere else I can try?

Today we discussed the design of our TV interfaces to be accessed via remote. The work has been split so each team member has one screen to design or some other piece of work.

We briefly discussed how shopping would work via the device. We considered the fact that if webservices were used, a single interface could be used for any supermarket. It was also suggested that one chain could make a bid for this service.

Discussing today, it was decided that the 'Reminders' section was probably unnecessary since the elderly are likely to use either a calendar or forget to use the service, which makes it redundant. It was decided that the one feature of that section regarding letting the system know when you leave the house, is probably best installed as a button or switch by the door (like a light switch) that can just be pressed as you leave.

Work to be completed
- Questionnaires to be filled out by Wednesday
- Screen Designs to be completed and emailed to Andy by the end of Wednesday if possible.

Andy - Stop-motion prototype video
Dan - Shopping Screen
Sam - Home Management Screen (Could you include a gas fire option in here?)
Anna - Welcome screen
Koulle - Research and ideas to do with sensors, placement and types required

Have I missed anything?

Work Splitting

As yet, we don't have a meeting Wednesday but I think we should meet up anyway to prototype and finish off last weeks work.

As a reminder, we've split up the work we've got to do in the following categories:

Interviews (Video, Questions) - Andy and Anna
Questionnaires - Koulle and Dan

Sam, I put you down to do some background research and define key use cases, but you can join one of the other groups if you want to. We may need someone else to interview in character!