SARAH GONG
ROOMMATE
website game
Centre for Digital Media, 2017.
For university students
Who need to apply for school dormitories
The ROOMMATE
Is a website game
That is linked to the school official housing website
Unlink universities’ own room arrangement systems which assign roommates randomly
Ours uses interesting games to collect users information, analyze users’ behaviors and give roommates recommendation.
Key features
-
Tailor to students at the University of British Columbia, Vancouver
-
Collect user behaviors and habits through games
-
Give recommendations for finding future roommates based on backend data and analysis
My contribution
Project and product management
-
Led in defining goals, scope, deliverables and roadmaps with team members.
-
Played a leading role in managing development process by using tools, such as Sprint, iterations, Kanban board, and retrospective, ensuring milestones and key deliverables were accomplished on schedule.
-
Boosted team performance by organizing peer learning activities, such as informal workshops on unity and website design.
-
Helped forming a closer team bonding by organizing team events after work, such as hot pot, pot luck, Pokémon competitions and school tours.
-
Took an active part in designing the user experience, such as user story, day in life, user flow, prototypes, wireframes and user testing.
-
Collaborated with software engineers to design the levels of two website games.
Design and development process
Forming a cohesive team

SWOT analysis

Development pipeline


Process:
1.Inception (Understand/Observe)
2.Elaboration (Define point of view/Ideate)
3.Construction (Prototype)
4.Transition (Test)
Design procedures

Research
1. School housing system research (four universities: UBC, SFU, BCIT, ECUAD)
2. Online questionnaire
3. Face-to-face interviews

Online questionnaire
Interviews

Brainstorming

Brainstorming keyword: roommate
Mind mapping

Mind map: likes

Mind map: dislikes
Persona
Storyboard


User story

User flow and wireframes

Iterations

User testing


Lessons learned

01. Process & milestones

02. Tools


OARRs
(objectives, Agendas, Roles, Rules)
Scrum

Sprint board


Bullseye
KFC (Keep, Fix, Change)
03. Software




04. Problem solving
1. Misdirection by initial concepts
2. Unclear scope
3. Lack of technical skills and experience

05. Teamwork
