You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

GR1 - Project Proposal and Analysis

User analysis

  • Persona 1: Novice user
    • General opinions: 
      • Useful thing to have. 
      • Without having to exchange multiple emails back and forth, you can schedule a meeting. It is convenient
    • Additional features: 
      • Reminder email for any change in plan. It is hard to get notified of sudden changes. It will be nice to get reminders if anything changes ( location, time etc.)
  • Persona 2: Power User
    • General opinions
      • Great idea, especially for users who have to constantly deal with scheduling meetings
    • Favorite Features
      • Being able to invite other people without having them log on
      • Having a recurrence option that can allow users to choose a day in the week to schedule a recurring event can help users because they don't need to recreate an event every time
    • Additional Features
      • An optimal message to be attached to the invite
      • A way to rank/select pre-scheduled flexible events that can be moved so it can be moved
  • Persona 3: Office Socialite
    • General opinions:
      • Only wants to use MashCal if it is easy to set up
      • Likes that he doesn't need to coordinate the optimal time for everyone
      • Wants to have everyone go to lunch with him. If the program says it can't happen, he doesn't have to feel bad about not accommodating everyone.
    • Additional features
      • Invites via text message
  • Persona 4: Dumbphone or non-mobile user 
    • General opinons
      • Adam liked the idea but thought it wouldn't be useful for him if it were mobile only.
    • Favorite features
      • Ability to import calendar once makes MashCal easy to use in the future because it is always in sync
      • Use of email as the communication medium means that even people without smartphones can use MashCal.
    • Additional Features
      • Make the interface not mobile only. There should be a standard, non-touch web interface.

Task analysis

Tasks:

Linking of calendars/create accounts,
  • Goal: 
    • To link/register users on to MashCal
  • Precondition: 
    • User want to create or join an event
  • PostCondition:
     
    • Have account,
    • Have calendars imported
    • Being able to create events
  • Subtask: 
    • Input login, 
    • Importing calendar

Create meeings:
  • Goal: 
    • Create a meeting 
  • Precondition: 
    • Have an account
  • Postcondition: 
    • Invitations sent, 
    • Subscription deadline set
  • Subtasks: Event recurence, deadline

Inviting people:
  • Goal: 
    • Sending invitations to people
  • Precondition: 
    • Existing event, 
    • Have intended users/ mail group (emailing list)
  • Postcondition: 
    • Users receive emails with a link
    • Event link created, 
  • Subtask: 
    • Choose group/emails 

View mashed events:
  • Goals: 
    • Browse through history of events
  • Precondition: 
    • Have an account; 
  • Subtask: 
    • Reschedule, edit events,
    • Filtering of events

Group circles:
  • Goal: Create a circle for your friends/email group
  • Precondition: 
    • Have an account, 
    • Have users emails/group
  • Postcondition: 
    • Have a group for quick inviting
  • Subtasks: 
    • Adding removing emails, 
    • Sending mails individually

TA Feedback.

As we discussed in our meeting, the project as it stands in this iteration is not a stretch. We discussed ways to improve that in our meeting, such as broadening the user population.

You don't seem to really get a good feel for what the tasks your users use to solve your problems, and instead you describe actions that your app will let users take. Don't forget that the next step is to make three separate designs - you shouldn't already have picked one. Think of task analysis as the analysis of tasks that need to be done to solve the problems.

You also don't address classes of users at all - these people aren't a complete set of people that are trying to solve these problems. You also only discuss how they'd feel about your app with users - go back and interview them about how they solve these problems in general. Please also remove the personally identifying information from your interview section.

I'd appreciate it if you made these changes, since we'll be working off this document for the whole rest of the project.

Revised User Analysis:

Person A

Uses email and facebook events to schedule events. No one ever confirms her invites. Has to call people the day of the event in order to get confirmations.

Person B

Mom scheduling for her kids. She keeps a schedule on a paper calendar and has to manually erase/update them for upcoming and changing events.

Person C
Person D
Person E
Person F
  • No labels