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

Compare with Current View Page History

« Previous Version 11 Next »

GR1 - BrackeTracker

Stephen Chang, Sarah Han, Samvaran Sharma

User analysis

There are a few personas who represent the main users of our product. To create each persona we have interviewed people who perform user class function:

  • the Manager
  • the Challenger
  • Manager/Challenger
  • for people who know how to use a computer and want a quick solution for creating a tournament
  • for people of all ages
  • need little-no previous experience
  •  

Phyllis the Traveler

Phyllis is a salesperson and an experienced traveler.  She works late almost everyday and is always looking for new ways to make her daily job more efficient, especially for tasks that do not directly impact her performance at her job.  She has three kids, and therefore wants to maximize the amount of time she spends at home.  She is comfortable with using the internet for her daily job, but she is not necessarily up to date with the newest cutting edge technology.  She finds that doing reimbursements is the worst part of her day, and most of the time has to take care of her expense reporting at home, because she is not allowed to bill those hours to her work.  Phyllis wants an interface that is easy to use and will save her a lot of time.

Lessons learned from a business consultant (Traveler persona):

Things already done well for expense reporting:

  • Company has their own homegrown system for business expenses
  • Air, hotel, car rental was automatically input from company AMEX

Things that are not done well with regard to expense reporting:

  • For mileage: "we end up estimating." This is likely a source of inaccuracy (at best) and bilking the system (at worst).

Manager:
current methods things that are done well:
MIT athleague - Captain/participant vs participant
other team also must confirm (one team confirm )
- resolving conflict (captain/manager)

needs work:
- visual bracket
-
Challenger:
participants:
mentally/verbally keeps tracks - i.e. most crude way (randomly pair ppl off)
keep track on a piece of paper

MarchMadness Bracket - write down 
One person writes down everything

Task analysis

There are a few main tasks involved with the Bracketracker.  These tasks include:

  • Create a tournament
  • Update the tournament
  • View your tournament(s)
  • Searching for and Joining tournament(s)
  • Manage a tournament

 

Create a Tournament

Searching/Joining a Tournament

Updating a Tournament

Managing a Tournament

Viewing a Tournament

Goal

To create a new tournament among friends & create a new bracket.

To join an existing tournament

Updating the score after a match

  • Send score confirmation request to opponent
  • Confirm score request

To ensure the tournament continues in a timely manner

  • Boot inactive players
  • Correct scores
  • Change tournament details

To assess state of the tournament:

  • View leaderboard
  • View scoreboard
  • View current bracket
  • View notifications

Preconditions

Type of tournament

Tournament name; If tournament in "joining" stage

Tournament name; which game/match; Score

Desire change

Tournament name;

Location

On website

On website

On website

On website

On website

Frequency of Use

Once per tournament

Once per tournament

Multiple times per day

As many as needed; many times a day

As many as needed; many times a day

How Learned

By doing or watching

By doing or watching

By doing or watching

By doing or watching

By doing or watching

Possible Errors

Non-Unique tournament name

Wrong tournament name; Missed "joining" period

Updating wrong game or score

Updating wrong feature or game

Being a dumbass

Time Constraints

None

Within "joining" period

Within scope of tournament

Within the scope of tournament

None

Who Else Involved

None

None

Opponent

None

None

  • No labels